Repository navigation
Make vault parity safe across coordinated cross-repository merges - #6
Merged
Merged
Conversation
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.
This follow-up addresses the merge-order observation. Pull requests still enforce exact source parity against the matching branch in MLT Player (or main if missing). Main pushes run the same check in advisory mode so a brief mismatch during an approved two-repository merge does not mark the whole build red. A lightweight scheduled daily job enforces strict parity after the merge window. Counterpart branch heads are resolved through
git ls-remoteand file content is fetched from the immutable commit SHA, avoiding stale raw.githubusercontent.com branch caches. No vault data-format or login behavior changes. Draft for CI and review; do not merge automatically.