fix(mirror): isolate downstream tag refs#4
Merged
Conversation
Fetch tag mirrors into mirror-specific remote-tracking refs so importing upstream content cannot create or overwrite downstream tags. Cover cache modes, cleanup, retained remotes, and exact tag-object preservation.
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.
Summary
Root cause
Tag fetches explicitly mapped upstream refs/tags/ into the downstream global tag namespace. Tag resolution also assumed that global destination.
Impact
Tag mirror add, pull, update, sync, diff, and status paths no longer create or overwrite downstream tags. Retained Braid remotes keep isolated tracking refs; normal remote cleanup removes them. Existing downstream tags are untouched.
Validation
All checks passed; golangci-lint reported 0 issues.