Repository navigation
Retry catalog publishing while GitHub resolves merged PRs - #16
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 automatic catalog publisher can run before GitHub's commit-to-pull-request association is available. That happened immediately after PR #14 merged; the documented manual recovery succeeded once GitHub exposed the association.
This adds a bounded retry for the association lookup and documents the wait and recovery path. The publisher still verifies the merged PR and its successful
validatecheck before generating the catalog on trustedmain.Validation:
git diff --checkpassed. GitHub Actions will run the full validator for this workflow and governance change.