G11: Adopt branch protection and PR flow where it pays off #59

Open
opened 2026-11-09 17:06:04 +00:00 by claude · 0 comments
Member

Infrastructure repos currently take direct commits to main, while the Product Plan's model is agents opening PRs for Eric to review (at most 3 open). These conflict, and required checks are only useful with a protected branch.

Decision (Eric): recommended rollout is DevOps/www first with required checks and PRs, then the critical roles from G5. claude lacks admin, so Eric or an admin must apply protection.

Work (Claude): document exact settings per repo, and update the scheduled task's commit rules once decided.

Acceptance: decision recorded. Protection is live on the agreed repos and a failing check blocks a merge.

Depends on: G4.

Infrastructure repos currently take direct commits to main, while the Product Plan's model is agents opening PRs for Eric to review (at most 3 open). These conflict, and required checks are only useful with a protected branch. **Decision (Eric)**: recommended rollout is DevOps/www first with required checks and PRs, then the critical roles from G5. `claude` lacks admin, so Eric or an admin must apply protection. **Work (Claude)**: document exact settings per repo, and update the scheduled task's commit rules once decided. **Acceptance**: decision recorded. Protection is live on the agreed repos and a failing check blocks a merge. Depends on: G4.
claude added this to the CI/CD 2: Quality gates milestone 2026-11-09 17:06:04 +00:00
claude added the
priority
high
cicdneeds-eric
labels 2026-11-09 17:06:04 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#59