Pull changes without changing branch#322
Merged
geofflamrock merged 4 commits intomainfrom Aug 21, 2025
Merged
Conversation
b16dc83 to
911e46d
Compare
bdd8b05 to
dbec2fd
Compare
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.
Currently when pulling changes for a stack, we change to each branch that is behind the remote and run
git pullon it. This isn't very efficient and can cause issues if there are changes in the working index, or if a branch in the stack is checked out in another worktree.This PR changes the way branches are pulled:
git pull origin {BranchName}.git -C {WorktreePath} pull origin {BranchName}to pull the changes in the other worktree location.git fetch origin {BranchName}:{BranchName}to fetch the changes directly into the branch without needing to change first.