Repository navigation
fix(guardrail): detect direct pushes using merged PR records - #56
Conversation
- Suppress alerts for commits recorded as merged pull requests into `main`, including rebase merges. - Alert on forced pushes and other direct branch updates, and fail when Slack delivery fails.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟢 Approval recommended
There are no active review issues for the guardrail workflow update.
No open issues 🎉
What changed in this PR
Updates the guardrail workflow to identify direct pushes to main using merged pull request records rather than committer names, supporting rebase merges.
Changes:
- Grants read access to pull requests and checks whether the pushed commit matches a merged PR.
- Always alerts on forced pushes and removes the Dependabot exemption.
- Passes push metadata through environment variables and fails on missing Slack configuration or HTTP delivery errors.
| File | Description |
|---|---|
.github/workflows/guardrail-audit-alert.yaml |
Replaces committer-based detection with PR lookups and strengthens Slack alert error handling. |
Review effort: Balanced
Summary
mainusing GitHub PR records rather than the committer name, including rebase merges.Dependencies
This PR is independent of the actionlint/uv tooling stack and targets the latest
maindirectly. It changes only.github/workflows/guardrail-audit-alert.yamland can merge in either order relative to that stack. No merge queue is required by the repository rules.Validation
git diff --checkpassed.Original commit:
5caedd994eaaf009618d4f9b5ac7b874f1ac964c.