fix: declaratively enforce allow_auto_merge in settings.yml#205
fix: declaratively enforce allow_auto_merge in settings.yml#205
Conversation
…low_auto_merge Adds the `repository` block to `.github/settings.yml` so that probot/settings declaratively manages `allow_auto_merge: true` and prevents future drift back to `null`. Also enforces `delete_branch_on_merge: true` and `has_wiki: false` per the org-wide standard defaults. The live GitHub API setting has been re-applied via PATCH to ensure immediate effect, and will now be maintained by probot/settings whenever the file is updated. Closes #163 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 46 minutes and 1 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 |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Makes GitHub repository settings compliant and drift-resistant by declaring them in .github/settings.yml so probot/settings can continuously enforce them.
Changes:
- Adds a
repositoryblock to declaratively enforceallow_auto_merge: true - Enables
delete_branch_on_merge: trueand disableshas_wiki: falseas standard defaults - Documents intent with references to the probot/settings project and internal standards
| # Repository-level settings — standard defaults | ||
| # Reference: https://github.com/petry-projects/.github/blob/main/standards/github-settings.md#repository-settings--standard-defaults | ||
| repository: | ||
| allow_auto_merge: true | ||
| delete_branch_on_merge: true | ||
| has_wiki: false |
There was a problem hiding this comment.
In probot/settings configs, repository: is expected at the YAML root. This file currently shows two-space indentation at the top-level (e.g., the initial comment lines are prefixed with two spaces in the diff view), which can be a signal that keys may not actually be at the root in the real file. If repository: ends up nested under another map due to leading indentation, probot/settings will ignore it and the compliance drift will continue. Ensure repository:, labels:, etc. are truly top-level (no leading indentation) in the actual YAML.
|
Summary
repositoryblock to.github/settings.ymlwithallow_auto_merge: true,delete_branch_on_merge: true, andhas_wiki: falseRoot cause
The compliance audit (
allow_auto_mergecheck) has been flagging this repo since the setting was not declared in.github/settings.yml. Although the setting was manually patched via API in prior sessions (PR #185 from 2026-04-14, still unmerged), the absence of a declarativerepositoryblock means the value can drift back tonullafter certain GitHub platform events. This PR makes the fix permanent by having probot/settings own the setting.Why not just merge PR #185?
PR #185 contains the same change, but since it has been open since April 14 without being merged, this PR supersedes it. PR #185 can be closed after this is merged.
Changes
.github/settings.yml: Addedrepositoryblock withallow_auto_merge: true,delete_branch_on_merge: true,has_wiki: falseCloses #163
Generated with Claude Code