Fix metadata routing and centrally schedule Autogrammar consumers - #1
Merged
Conversation
This was referenced Sep 5, 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
1 participant
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.
A migrated repository such as autogrammar/imgl dispatched to semcod/.github, where the receiver stripped its owner and attempted to sync semcod/imgl. The child workflow also failed because Autogrammar has no ORG_SYNC_PAT.
Resolve full repository identities from event JSON and manage four explicit Autogrammar projects from the existing six-hour coordinator schedule. Foreign targets update descriptions/topics only, preserving homepage, Pages and profiles. Reject unmanaged targets, report individual sync failures through a nonzero exit, verify the REST private field, and prevent profile writes across owners. Bootstrap checks canonical remotes, preserves dirty work and skips centrally scheduled targets.
Validation: 19 regression tests pass, covering routing, input handling, private repositories, profile ownership, failure propagation and bootstrap behavior. Workflow YAML parses. Canonical instructions are in docs/information/org-metadata-sync.md with an index; existing setup pages link there. Hosted dry-run and actual permission/readback checks precede retiring child triggers.