Repository navigation
Preserve checkout safety and conflict staging during pull - #51
Merged
Merged
Conversation
Saanvi521
changed the title
aman-a-shah
changed the title
aman-a-shah
approved these changes
Oct 25, 2026
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.
Keep conflicted paths at their pre-merge index entries while writing conflict markers to the working tree, so explicit
addrecords resolution. Add working-tree regressions for downloaded trees, deletions, nested files, executable modes, binary/Unicode content, unsafe checkout, and read-only status/diff.Reconciled with current main without losing its safe staging, persistent merge resolution, or executable-mode handling.
Closes #39.
Validation:
scripts/quality-check.shcovers the complete suite, including 12 new checkout and merge-result tests.