Skip to content

Omit repo guard comment when PR comes from fork - #483

Open
metapileks wants to merge 1 commit into
developfrom
pileks/met-620-repository-guard-fails-on-fork-prs-comment-step-gets-403
Open

Omit repo guard comment when PR comes from fork#483
metapileks wants to merge 1 commit into
developfrom
pileks/met-620-repository-guard-fails-on-fork-prs-comment-step-gets-403

Conversation

@metapileks

@metapileks metapileks commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

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.

  • Appends the generated guard report to GITHUB_STEP_SUMMARY.
  • Skips comment lookup and creation for fork-originated pull requests.
  • Leaves the final repository-guard gate active for both fork and same-repository pull requests.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains in the changed workflow behavior.

Important Files Changed

Filename Overview
.github/workflows/repo-guard.yml Adds an unconditional run summary and safely guards both write-comment actions for fork pull requests without affecting the final failure gate.

Reviews (2): Last reviewed commit: "Omit repo guard comment when PR comes fr..." | Re-trigger Greptile

@metapileks
metapileks requested a review from meta-reid August 4, 2026 15:41
@metapileks metapileks self-assigned this Aug 4, 2026
@metapileks
metapileks requested a review from metanallok as a code owner August 4, 2026 15:41
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Repository Guard

  • Cargo.lock: pass
  • yarn.lock (root): pass
  • yarn.lock (sdk): pass
  • Repo guard: pass

Repository Guard

Cargo dependency pinning

  • Status: pass
  • Every programs/*/Cargo.toml dep uses =x.y.z, a path = .. workspace ref, or a git dep with a 40-char rev.

Cross-program Anchor/Solana version consistency

  • Status: pass
  • anchor-lang and anchor-spl are pinned to the version declared in repo-guard.toml across every program.

solana-program crate pin

  • Status: pass
  • Every solana-program = "=X" declaration is =1.17.14 (locked to match Cargo.lock).

Anchor.toml solana_version

  • Status: pass
  • Anchor.toml declares solana_version = "1.17.34" (local-dev install for anchor test).

Crate minimum age

  • Status: pass
  • All Cargo deps changed by this PR are at least 14 days old on crates.io.

Yarn package.json pinning

  • Status: pass
  • All package.json deps use exact versions (no ^, ~, ranges).

npm minimum age

  • Status: pass
  • All npm deps changed by this PR are at least 14 days old.

Workflow toolchain consistency

  • Status: pass
  • Every workflow declares anchor-version: 0.29.0.
  • Per-file solana-cli-version values match [toolchain.workflow_solana_cli] in repo-guard.toml.

GitHub Action SHA pinning

  • Status: pass
  • Every third-party action is pinned to a SHA in [actions.sha_allowlist].

Sensitive program / config changes

  • Status: warn
  • Review hint only (CODEOWNERS is the merge gate). Lines below match heuristics for security-sensitive changes:
  • High-sensitivity files touched: .github/workflows/repo-guard.yml

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants