fix: enable delete_branch_on_merge for compliance#184
fix: enable delete_branch_on_merge for compliance#184
Conversation
Enables automatic deletion of head branches after PR merge, as required by the org standard for repository settings. Closes #164 Co-authored-by: don-petry <don-petry@users.noreply.github.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 45 minutes and 33 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
@don-petry — PR is ready for review and merge. This adds |
|
There was a problem hiding this comment.
Pull request overview
Enables the GitHub repository setting to automatically delete head branches after pull requests are merged, via probot/settings, to meet the organization’s repository settings standard and resolve compliance issue #164.
Changes:
- Adds a top-level
repositoryblock to.github/settings.yml. - Sets
delete_branch_on_merge: truewith an inline reference to the org standard.
Automated review — APPROVEDRisk: LOW SummarySingle-line config addition to .github/settings.yml enabling delete_branch_on_merge via probot/settings for org compliance. All CI checks pass (SonarCloud quality gate passed, 0 new issues/hotspots, CodeQL clean, AgentShield green). Triage escalated only due to triage-output-invalid signal, not a real security concern. FindingsInfo
CI statusAll CI checks pass: SonarCloud quality gate passed (0 new issues/hotspots), CodeQL clean, AgentShield green. Reviewed by the don-petry PR-review cascade (triage: haiku 4.5 → deep: sonnet 4.6 + duck: gpt-5.4 → audit: opus 4.6). Reply with |
|
Superseded by #200 which contains the same fix on the active branch. |



Summary
delete_branch_on_merge: trueto.github/settings.ymlso probot/settings automatically enables the "Automatically delete head branches" repository settingCloses #164
Generated with Claude Code