chore: declare allow_auto_merge in settings.yml for compliance

[don-petry]

Summary

• Adds allow_auto_merge: true to .github/settings.yml so probot/settings enforces the setting as policy-as-code
• The live repository setting was also explicitly set via the GitHub API to ensure the next compliance audit sees true rather than null

Root Cause

The weekly compliance audit checks allow_auto_merge via the GitHub API. The field returns null when it hasn't been explicitly set via the API (even if the UI shows it as enabled). PR #122 made the same settings.yml change but was never merged, so the finding persisted.

This fix:

1. Directly called PATCH /repos/petry-projects/broodly with allow_auto_merge=true to immediately remediate the live setting
2. Codifies the setting in settings.yml so probot/settings keeps it enforced and prevents future drift

Changes

• .github/settings.yml — added allow_auto_merge: true under the repository: block

Closes #105

Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated repository settings to enable automated merge functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

A single configuration line is added to .github/settings.yml to enable GitHub's auto-merge functionality, setting repository.allow_auto_merge: true to comply with repository settings standards.

Changes

Cohort / File(s)	Summary
GitHub Settings Configuration .github/settings.yml	Enable auto-merge feature by adding repository.allow_auto_merge: true property.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: enabling allow_auto_merge in settings.yml for compliance purposes.
Linked Issues check	✅ Passed	The PR directly addresses issue #105 by enabling allow_auto_merge in settings.yml and configuring it via the GitHub API, meeting all stated requirements.
Out of Scope Changes check	✅ Passed	The single change to .github/settings.yml is directly scoped to the compliance requirement stated in issue #105.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-105-20260420-0333

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[don-petry]

@don-petry This PR is ready for review and merge. It fixes the allow_auto_merge compliance finding by declaring allow_auto_merge: true in .github/settings.yml so probot/settings enforces it as policy-as-code. The live setting was also explicitly set via the GitHub API to immediately remediate the finding before the next weekly audit.

[Copilot]

Pull request overview

This PR codifies the repository’s auto-merge compliance setting by declaring allow_auto_merge: true in probot/settings, ensuring the compliance audit (issue #105) sees an explicit true rather than null via the GitHub API.

Changes:

• Add allow_auto_merge: true under the repository: block in .github/settings.yml.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

🧹 Nitpick comments (1)

.github/settings.yml (1)

8-10: Ensure branch protection rules are configured when enabling auto-merge.

When enabling allow_auto_merge, verify that branch protection rules on your main/target branches require:

• Minimum number of approving reviews
• Status checks to pass before merging
• Up-to-date branches (if applicable)

This ensures auto-merge (especially for Dependabot PRs) cannot bypass your review and quality gates.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/settings.yml around lines 8 - 10, The repository config enables
allow_auto_merge but lacks branch protection settings; update the GitHub
settings to add branch protection rules for main/target branches (e.g., add
required_pull_request_reviews with a minimum approval count,
required_status_checks with the list of checks that must pass, and
require_up_to_date_branch/strict status for up-to-date branches) so auto-merge
cannot bypass review or CI gates—apply these rules alongside the existing
repository keys (repository, has_discussions, allow_auto_merge).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/settings.yml:
- Around line 8-10: The repository config enables allow_auto_merge but lacks
branch protection settings; update the GitHub settings to add branch protection
rules for main/target branches (e.g., add required_pull_request_reviews with a
minimum approval count, required_status_checks with the list of checks that must
pass, and require_up_to_date_branch/strict status for up-to-date branches) so
auto-merge cannot bypass review or CI gates—apply these rules alongside the
existing repository keys (repository, has_discussions, allow_auto_merge).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8f8902d6-1fb0-4c35-bf28-fec671935fa8

📥 Commits

Reviewing files that changed from the base of the PR and between 9a6419e and 419abf6.

📒 Files selected for processing (1)

• .github/settings.yml

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

@dev-lead - please fix this PR

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Closing due to merge conflict that cannot be auto-rebased. Re-implementing from fresh main via dev-lead.