fix(add): remove checkout_tree call on bare repo during fast-forward - #16
Merged
Merged
Conversation
0x56696B
marked this pull request as ready for review
May 5, 2026 10:22
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
1 participant
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.
Summary
checkout_tree()is illegal on bare repos — pygit2 raisescannot checkout. This operation is not allowed against bare repositorieshead.set_target()was redundant — HEAD is a symbolic ref pointing to the branch; updating the branch ref is sufficientlookup_reference().set_target()Test plan
git-wt add <new-branch> mainfrom inside a bare repo wheremainhas diverged from origin — should fast-forward without crashinggit-wt add <new-branch> mainwheremainis already up to date — should continue working as before