Repository navigation
Fix catalog publishing for merged fork submissions - #13
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
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.
The publisher could not add merged fork submissions to the catalog because public fork pull-request workflows receive a read-only
GITHUB_TOKEN; merged bot PR #12 therefore passed validation but failed at the catalog push.This moves publication to a trusted
mainpush. The publisher resolves the merged PR associated with that commit, requires a successfulvalidatecheck on the PR head, then regenerates the catalog frommainwithout running submitted bot code. Aworkflow_dispatchrecovery path republishes an already merged submission such as #12.GOVERNANCE.mdnow documents the required token scopes, GitHub Actions workflow permission setting, branch-rule requirement, and maintainer approval for fork validation runs.README.mdlinks to that guidance.Validation:
git diff --checkpassed, and GitHub's commit-to-PR API associates #12's merge commit with PR #12 as this workflow expects. The PR validation workflow will run on this change.