Skip to content

fix: enable delete_branch_on_merge for compliance#184

Open
don-petry wants to merge 2 commits intomainfrom
claude/issue-164-20260414-1130
Open

fix: enable delete_branch_on_merge for compliance#184
don-petry wants to merge 2 commits intomainfrom
claude/issue-164-20260414-1130

Conversation

@don-petry
Copy link
Copy Markdown
Collaborator

Summary

  • Adds delete_branch_on_merge: true to .github/settings.yml so probot/settings automatically enables the "Automatically delete head branches" repository setting
  • Brings the repository into compliance with the org standard for repository settings

Closes #164

Generated with Claude Code

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>
Copilot AI review requested due to automatic review settings April 14, 2026 11:31
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 45 minutes and 33 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e892116d-fb2b-4b8b-8d86-e366892e0242

📥 Commits

Reviewing files that changed from the base of the PR and between 32e618b and 8406ac6.

📒 Files selected for processing (1)
  • .github/settings.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/issue-164-20260414-1130

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@don-petry
Copy link
Copy Markdown
Collaborator Author

@don-petry — PR is ready for review and merge. This adds delete_branch_on_merge: true to .github/settings.yml to bring the repo into compliance with the org standard.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 repository block to .github/settings.yml.
  • Sets delete_branch_on_merge: true with an inline reference to the org standard.

@don-petry
Copy link
Copy Markdown
Collaborator Author

Automated review — APPROVED

Risk: LOW
Reviewed commit: 89cc303f4eb4c41c0cb12236e393d9abc1c193de
Cascade: triage → deep (see triage: haiku 4.5 → deep: sonnet 4.6 + duck: gpt-5.4 → audit: opus 4.6 for models)

Summary

Single-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.

Findings

Info

  • [info] .github/settings.yml:4 — Adds delete_branch_on_merge: true to bring repo into compliance with org standard. Closes Compliance: delete_branch_on_merge #164. No security, correctness, or maintainability concerns.

CI status

All 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 @don-petry if you need a human.

@don-petry
Copy link
Copy Markdown
Collaborator Author

Superseded by #200 which contains the same fix on the active branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compliance: delete_branch_on_merge

2 participants