Working Copy Discard does not discard unstaged submodule changes

strich August 12, 2013

Given a simple Git setup with at least 1 submodule repository, make a change within the submodule. Now, you want to update your current branch to the latest but it will fail due to unstaged changes in the submodule. Discarding Working Copy changes will succeed but it will not discard unstaged changes within the submodule.

Fixing this problem requires the user to have to realise the unstaged changes within the submodule, specifically access it, discard the changes, then go back to the parent branch and finally perform a Pull.

Would be great if we could simply this process a bit to have Working Copy->Discard properly discard all unstaged changes in children submodules.

2 answers

0 votes
strich August 12, 2013

Windows v1.0.8.0.

0 votes
KieranA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 12, 2013

Is this for Mac or Windows?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events