Repository navigation
fix: stash before fast-forwarding in a worktree - #156
Merged
Merged
Conversation
* Issue: Fast-forward a branch checked out in a worktree ran `git merge --ff-only` without stashing, so it failed whenever uncommitted changes touched a file that an upstream commit changed * Fix: Stash around the fast-forward too
Contributor
Author
|
Contributor
Author
|
How to reproduce bug Run in an empty directory: Issue result: |
Owner
|
Thanks for finding and fixing this! |
Owner
|
This is now released in v2.6.1. Thanks again! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
git merge --ff-onlywithout stashing, so it failed whenever uncommitted changes touched a file that an upstream commit changed