chore(pylon): harden fork synchronization - #7
Merged
Conversation
Use GitHub fork synchronization behind a fail-closed exact-main ruleset, keep review candidates idempotent, and retain verified CI evidence without adding a privileged token.
16 tasks
This was referenced Aug 30, 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.
Problem
The mirror workflow updates
mainwith a direct Git push and carries an optional App-token path. That prevents us from locking the mirror branch without either weakening protections or exposing a credential that could trigger inherited upstream publication.Fix
mainthrough GitHub's forkmerge-upstreamAPI only after a readable, exact-main repository ruleset proves the workflow token cannot bypass the update, deletion, linear-history, and non-fast-forward rules;build-check-testaggregate succeeded; otherwise rerun verification;The workflow intentionally fails closed until the live repository ruleset is provisioned. After this lands, maintainers must enable squash merging as GitHub's linear-history prerequisite, create and audit the zero-bypass exact-main ruleset, remove the superseded classic
mainprotection, and validate a real dispatch before calling the mirror locked.Verification
bash -n scripts/pylon-sync-upstream.shshellcheck scripts/pylon-sync-upstream.shactionlint .github/workflows/pylon-upstream-sync.ymlgit diff --checknpm run checkvia the signed commit hookRefs #1.
Implemented by GPT-5.6 in Prime Agent, orchestrated through Pylon.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.