Retry GitHub PR metadata reads in shared checks#88
Merged
Conversation
laurenleach
approved these changes
May 28, 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.
Why
Two Axiomatic connector PRs failed required shared checks when workflow-scoped GitHub API reads returned 404 for valid PR metadata endpoints. A same-minute Axiomatic PR passed the same shared workflow commit, and connector verify plus metadata checks passed, so the failure is isolated to PR metadata reads rather than connector code.
This keeps the trust boundary unchanged: the workflows do not fall back to reading additional PR checkout content under elevated permissions.
What this changes
Validation
Draft until the affected connector PR checks can be rerun against this workflow change.