Skip to content

ci: enable main branch protection (PR-E)#27

Merged
ernestprovo23 merged 1 commit into
mainfrom
ci/pr-e-branch-protection
Jun 9, 2026
Merged

ci: enable main branch protection (PR-E)#27
ernestprovo23 merged 1 commit into
mainfrom
ci/pr-e-branch-protection

Conversation

@ernestprovo23

Copy link
Copy Markdown
Member

Summary

  • Made repo public to unlock branch protection on GitHub Free plan
  • Applied branch protection to main via gh api -X PUT repos/ernestprovo23/conclave/branches/main/protection
  • Documents the applied config in .github/branch-protection.json

Protection config applied

Setting Value
Required status checks pytest/py3.11, pytest/py3.12, pytest/py3.13, ruff, gitleaks
Require branches up to date true (strict=true)
Enforce admins false (admin merge allowed)
Required PR reviews none (sole maintainer)
Force pushes blocked
Branch deletions blocked

Verification

gh api repos/ernestprovo23/conclave/branches/main/protection \
  --jq '{enforce_admins: .enforce_admins.enabled, required_status_checks: .required_status_checks.contexts, strict: .required_status_checks.strict}'

Output confirms all 5 checks registered, strict=true, enforce_admins=false.

Test plan

  • All 5 CI checks pass on this PR
  • Branch protection is active (verify via repo Settings > Branches)

Applied via: gh api -X PUT repos/ernestprovo23/conclave/branches/main/protection

Required status checks (all must pass before merge):
  - pytest / py3.11
  - pytest / py3.12
  - pytest / py3.13
  - ruff
  - gitleaks

Settings: strict=true (branches must be up to date), enforce_admins=false
(admin can still merge), no PR review requirement (sole maintainer).
Repo made public to enable branch protection on free plan.
@ernestprovo23
ernestprovo23 merged commit 66cc044 into main Jun 9, 2026
5 checks passed
@ernestprovo23
ernestprovo23 deleted the ci/pr-e-branch-protection branch June 10, 2026 00:08
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.

1 participant