Block fork pull request workflow jobs - #1
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
🧰 Additional context used🔀 Multi-repo context coderabbitai/bitbucketLinked repositories findingscoderabbitai/bitbucket
Summary: The repository contains GitHub Actions workflows that consume repository secrets; the PR's change to skip jobs for fork pull requests will prevent those secrets from being exposed to forked-PR workflows. No other cross-repo consumers or shared contracts were found. 🔇 Additional comments (1)
📝 WalkthroughWalkthroughThis PR adds conditional execution guards to two GitHub Actions workflow jobs. Both the ChangesWorkflow Job Execution Gating
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Summary
Why
Public fork pull requests can run attacker-controlled workflow code. Skipping those jobs prevents those pull requests from reaching repository secrets through GitHub Actions.
Validation
yq e '.'.Summary by CodeRabbit