Skip to content

chore: branch-protection JSON + apply workflow + artifact cleanup + CodeQL#54

Merged
constk merged 1 commit into
developfrom
feat/14-protection-apply
Apr 26, 2026
Merged

chore: branch-protection JSON + apply workflow + artifact cleanup + CodeQL#54
constk merged 1 commit into
developfrom
feat/14-protection-apply

Conversation

@constk
Copy link
Copy Markdown
Owner

@constk constk commented Apr 26, 2026

Closes #14. Adds the three workflows that complete the branch-protection / artifact-hygiene / static-analysis story; JSONs already shipped in #10.

…odeQL (#14)

The JSON specs (.github/branch-protection/{develop,main}.json + README.md)
already shipped in #10. This PR adds the three remaining workflows that
operate against them or alongside them:

- branch-protection.yml — applies the JSON spec to main + develop on schedule
  (Monday 06:00 UTC), workflow_dispatch, and push to main when the spec or
  workflow itself changes. Requires a BRANCH_PROTECTION_TOKEN secret with
  admin:repo scope (default GITHUB_TOKEN cannot edit branch protection on
  the repo it runs in). Step summary diffs before/after each apply.
- artifact-cleanup.yml — weekly artifact pruning (default 7 days, scheduled
  live, manual dry-run by default). Stops the account-wide artifact quota
  from accumulating.
- codeql.yml — placeholder. workflow_dispatch only until the repo is public
  (or gains a GHAS subscription). All `on:` triggers commented in-file with
  the re-activation recipe.

All four workflows are EXEMPT_WORKFLOWS in check_required_contexts.py
(scheduled / dispatch-only / push-to-main-only); the meta-gate stays in
sync at 12 required contexts.

Closes #14

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@constk constk merged commit 85fd2ec into develop Apr 26, 2026
@constk constk deleted the feat/14-protection-apply branch April 26, 2026 17:19
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