Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up`Repository.mergeBranches` leaves HEAD with a dirty index after the merge #1271
Conversation
Force a complete checkout to wipe the index of any staged changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
rcjsuen commentedApr 12, 2017
So for whatever reasons, creating a commit off of the written index doesn't seem to wipe the index clean of its changes. While I don't think the proposed change is really the best way to fix #1217, it does get the index into a clean state.