chore(settings): add .github/settings.yml to codify repo settings#118
chore(settings): add .github/settings.yml to codify repo settings#118
Conversation
Documents required repository settings per the petry-projects org standard (standards/github-settings.md), including `delete_branch_on_merge: true`. This creates an auditable, reviewable infrastructure-as-code record of the intended settings. The Probot GitHub Settings app will enforce these automatically if installed in the future; for now, settings are applied via the GitHub API (apply-repo-settings.sh). Closes #92 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 52 minutes and 3 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 this PR adds |
|
There was a problem hiding this comment.
Pull request overview
Adds a Probot GitHub Settings–format file to codify this repository’s GitHub settings in-repo, primarily to address compliance around delete_branch_on_merge and to make settings auditable.
Changes:
- Adds
.github/settings.ymldescribing required GitHub repository settings (issues/wiki/discussions + merge settings). - Codifies
delete_branch_on_merge: trueand squash merge commit formatting options.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # These settings are enforced via the GitHub API (scripts/apply-repo-settings.sh). | ||
| # If the Probot GitHub Settings app is ever installed, this file will also | ||
| # automatically enforce them. |
There was a problem hiding this comment.
The comment references scripts/apply-repo-settings.sh, but this repository doesn’t contain a scripts/ directory or that script. This is misleading for future maintainers—please update the comment to point at the actual location of the org script (or link to the standard/docs that describe how settings are applied).
| # These settings are enforced via the GitHub API (scripts/apply-repo-settings.sh). | |
| # If the Probot GitHub Settings app is ever installed, this file will also | |
| # automatically enforce them. | |
| # These settings are defined by the organization standard above and may be | |
| # enforced automatically if the Probot GitHub Settings app is installed. |
Summary
.github/settings.ymldocumenting required repository settings per the petry-projects org standarddelete_branch_on_merge: truevia the GitHub API (confirmed active)Why a settings file?
Previous fixes (April 14, April 18) applied the setting via the GitHub API but left no code change in the repository. This PR creates an auditable, reviewable record of the intended settings in
.github/settings.ymlusing the Probot GitHub Settings format — a widely-recognized standard. If the app is ever installed org-wide, enforcement becomes automatic. Until then, settings are applied via the org'sapply-repo-settings.shscript.Compliance
The
delete_branch_on_mergesetting is currentlytruein the GitHub API (re-verified and re-applied as part of this fix). The next weekly Friday audit should clear the finding.Closes #92
Generated with Claude Code