Pin GitHub Actions to commit SHAs and scope workflow permissions#79
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: loadsmart/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe PR updates the ChangesWorkflow Security and Reproducibility
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Deploy Preview for loadsmart-engineering ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Actionable comments posted: 0 |
rodsenra
left a comment
There was a problem hiding this comment.
lgtm. Thanks for the attentive work @marcelomagina
Types of changes
Chore (CI security hardening)
Description of the proposed changes
Hardens the
new-post.ymlworkflow based on azizmorstatic analysis of the repo's GitHub Actions:read-blog-post-contentandnotify-of-new-blog-post-to-reviewwere referenced via the mutable@masterref ofloadsmart/github-actions. Anyone able to push to that repo'smaster(or a compromise of it) would flow straight into this workflow with the repo token. Both are now pinned to a commit SHA with a# mastercomment for readability.actions/checkout. Was@v2(unpinned + outdated); now pinned to thev4.2.2commit SHA, withpersist-credentials: falseso the token isn't left on disk.notify-if-blog-postjob ran with the default (broad)GITHUB_TOKEN; it only needscontents: read, which is now set explicitly.After these changes
zizmorreports no findings for this workflow.Screenshots
N/A — CI configuration change only.
Summary by CodeRabbit