Skip to content

fix: add repository block to settings.yml for allow_auto_merge#218

Open
don-petry wants to merge 2 commits intomainfrom
claude/issue-163-20260419-2233
Open

fix: add repository block to settings.yml for allow_auto_merge#218
don-petry wants to merge 2 commits intomainfrom
claude/issue-163-20260419-2233

Conversation

@don-petry
Copy link
Copy Markdown
Collaborator

Summary

  • Adds repository block to .github/settings.yml with allow_auto_merge: true so the setting is declaratively managed via probot/settings
  • Also adds delete_branch_on_merge: true and has_wiki: false to match the full standard defaults
  • Re-applied the setting via GitHub API for immediate effect

Root Cause

The compliance audit has been finding allow_auto_merge: null periodically. While the API-level setting gets patched to true, without it being declared in .github/settings.yml, probot/settings can reset it on subsequent runs. This PR makes the setting authoritative and prevents future drift.

Note: PR #185 contains the identical fix but has not been merged. This supersedes it.

Closes #163

Generated with Claude Code

Declaratively manage allow_auto_merge: true via probot/settings to
prevent future drift. Also adds delete_branch_on_merge: true and
has_wiki: false to match standard defaults.

Closes #163

Co-authored-by: don-petry <don-petry@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 19, 2026 22:35
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 19, 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 46 minutes and 13 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 46 minutes and 13 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: a5077dc0-4d2a-44ff-88f3-2d643c93282a

📥 Commits

Reviewing files that changed from the base of the PR and between 32e618b and 6b38a26.

📒 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-163-20260419-2233

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

Self-review complete - change adds the repository block to .github/settings.yml with allow_auto_merge: true, delete_branch_on_merge: true, and has_wiki: false. Format is correct for probot/settings. CI is passing. Note: PR 185 contains the identical fix but has been waiting for merge since 2026-04-14, this PR supersedes it. @don-petry as CODEOWNER, please review and merge to resolve the recurring compliance audit finding.

@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

This PR makes allow_auto_merge (and related standard repository settings) declaratively managed via probot/settings by adding a repository block to .github/settings.yml, preventing the setting from drifting back to null on subsequent runs.

Changes:

  • Added a repository section to .github/settings.yml with allow_auto_merge: true
  • Also set delete_branch_on_merge: true and has_wiki: false to match the referenced standard defaults

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: allow_auto_merge

2 participants