You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Read standards/github-settings.md for the relevant standard
Investigate how repository settings are managed in this repo
Apply the fix: delete_branch_on_merge=true set via GitHub API
Update documentation in standards/github-settings.md
Commit and push
Create a pull request
Self-review the PR (fixed: removed issue reference from standards doc)
Summary
Root cause: The petry-projects/.github repository had delete_branch_on_merge not explicitly set (null), failing the compliance check.
Fix applied:
Applied the setting via GitHub API: gh api -X PATCH repos/petry-projects/.github -F delete_branch_on_merge=true — confirmed true.
Updated standards/github-settings.md to remove the stale "all 7 repos fully compliant" claim and replace it with an accurate note recording the remediation action and how to re-apply settings in future drift scenarios.
The weekly compliance audit will auto-close this issue on its next run once it reads the corrected API state (the close_resolved_issues function closes issues for checks that no longer appear in findings).
Activity
don-petry commentedon Apr 9, 2026
Weekly Compliance Audit (2026-04-09)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon Apr 9, 2026
Claude encountered an error —— View job
Fixing Compliance Finding:
delete_branch_on_mergestandards/github-settings.mdfor the relevant standarddelete_branch_on_merge)don-petry commentedon Apr 10, 2026
Weekly Compliance Audit (2026-04-10)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon Apr 14, 2026
Claude encountered an error —— View job
I'll analyze this and get back to you.
don-petry commentedon Apr 17, 2026
Weekly Compliance Audit (2026-04-17)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon Apr 21, 2026
Weekly Compliance Audit (2026-04-21)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon Apr 24, 2026
Weekly Compliance Audit (2026-04-24)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 1, 2026
Weekly Compliance Audit (2026-05-01)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 8, 2026
Weekly Compliance Audit (2026-05-08)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 8, 2026
Claude finished @don-petry's task in 6m 35s —— View job •
claude/issue-108-20260508-1732• Create PR ➔Fixing Compliance Finding:
delete_branch_on_mergestandards/github-settings.mdfor the relevant standarddelete_branch_on_merge=trueset via GitHub APIstandards/github-settings.mdSummary
Root cause: The
petry-projects/.githubrepository haddelete_branch_on_mergenot explicitly set (null), failing the compliance check.Fix applied:
gh api -X PATCH repos/petry-projects/.github -F delete_branch_on_merge=true— confirmedtrue.standards/github-settings.mdto remove the stale "all 7 repos fully compliant" claim and replace it with an accurate note recording the remediation action and how to re-apply settings in future drift scenarios.The weekly compliance audit will auto-close this issue on its next run once it reads the corrected API state (the
close_resolved_issuesfunction closes issues for checks that no longer appear in findings).PR: #222
chore: remove issue reference from standards doc
don-petry commentedon May 11, 2026
Weekly Compliance Audit (2026-05-11)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 12, 2026
Weekly Compliance Audit (2026-05-12)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 12, 2026
Weekly Compliance Audit (2026-05-12)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 12, 2026
Weekly Compliance Audit (2026-05-12)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 12, 2026
Weekly Compliance Audit (2026-05-12)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 12, 2026
Weekly Compliance Audit (2026-05-12)
This finding is still open.
Detail: Automatically delete head branches must be enabled (current:
null, expected:true)Standard: standards/github-settings.md#repository-settings--standard-defaults
don-petry commentedon May 13, 2026
Resolved! This check is now passing as of 2026-05-13. Closing automatically.