Omit repo guard comment when PR comes from fork - #483
Open
metapileks wants to merge 1 commit into
Open
Conversation
…uard comment in run summary
Contributor
|
Repository Guard
Repository GuardCargo dependency pinning
Cross-program Anchor/Solana version consistency
solana-program crate pin
Anchor.toml solana_version
Crate minimum age
Yarn package.json pinning
npm minimum age
Workflow toolchain consistency
GitHub Action SHA pinning
Sensitive program / config changes
Overall status: pass Lockfile freshness (Cargo.lock + yarn.lock) is checked by the workflow directly and cannot be bypassed. The sensitive-diff section is a review hint - CODEOWNERS handles the actual merge gate. |
meta-reid
approved these changes
Aug 4, 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.
Always render repo guard comment in run summary
See https://github.com/metaDAOproject/programs/actions/runs/30925405694?pr=483 for example
Greptile Summary
The workflow now publishes repository-guard results to the GitHub Actions run summary for every pull request while limiting PR-comment operations to same-repository branches.
GITHUB_STEP_SUMMARY.Confidence Score: 5/5
The PR appears safe to merge.
No blocking failure remains in the changed workflow behavior.
Important Files Changed
Reviews (2): Last reviewed commit: "Omit repo guard comment when PR comes fr..." | Re-trigger Greptile