Repository navigation
Integrate fetched tips through the merge engine and harden refs - #59
Merged
Merged
Conversation
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.
Pull needs to integrate a downloaded commit without bypassing checkout, merge conflicts, or inactive-branch protections. Add
CommitManager.integrate_fetched_tip, validate complete fetched history before integration, and publish ref files atomically. Nested branches are listed recursively; ref paths reject whitespace/control characters, symlinks, and file/directory collisions.Closes #40.
Validation:
scripts/quality-check.shpasses locally with 320 tests, including fetched fast-forwards, no-ops, clean merges, conflict resolution, inactive branches, failed ref publication, and unsafe ref paths.