Repository navigation
fix(guardrail): detect direct pushes using merged PR records - #54
Conversation
|
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 55 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
No active review issues are reported for the guardrail workflow update.
No open issues 🎉
What changed in this PR
Updates the repository’s guardrail workflow to identify merges into main using merged PR records rather than committer names, including support for rebase merges.
Changes:
- Matches pushed SHAs against merged PRs targeting this repository’s
main. - Treats forced updates as alert-worthy and removes the Dependabot exemption.
- Adds PR read permission and explicit failure handling while preserving safe Slack JSON construction.
| File | Description |
|---|---|
.github/workflows/guardrail-audit-alert.yaml |
Replaces committer-based detection with PR-record checks and strengthens Slack delivery error handling. |
Review effort: Balanced
Summary
mainby matching the pushed SHA to GitHub's merged-PR records instead of relying on the committer name, including rebase merges.Dependencies
This PR changes only
.github/workflows/guardrail-audit-alert.yamland is based directly onupstream/main, independently of the actionlint PR. The PRs can merge in either order. The workflow matchesFramework-R-D/action-generate-build-matrix#56byte-for-byte.Validation
git diff --checkpassed and the complete staged diff was inspected.