Require the ci / build-dev-base status context in branch protection #457

Closed
opened 2026-07-10 22:07:42 +00:00 by coilyco-ops · 1 comment
Owner

Follow-up from #454 / PR #456, which added a build-dev-base job to ci.yml: every pull request now builds the whole dev-base tier family build-only through the shared actions/dev-base-build composite. The remaining step is admin-side: add ci / build-dev-base to the required status contexts in this repo's branch protection, alongside the existing ci / gate, so a red image build blocks the merge.

The engineer container's token gets 403 on /branch_protections (needs owner/admin), so Kai or an admin surface applies this by hand or via ward ops forgejo admin verbs. One caveat to time it with: PRs opened before #454 landed will not produce the new context until rebased onto a main that carries the job.

Refs: #454, #452, docs/pr-dev-base-build-validation.md.

Follow-up from #454 / PR #456, which added a `build-dev-base` job to ci.yml: every pull request now builds the whole dev-base tier family build-only through the shared `actions/dev-base-build` composite. The remaining step is admin-side: add `ci / build-dev-base` to the required status contexts in this repo's branch protection, alongside the existing `ci / gate`, so a red image build blocks the merge. The engineer container's token gets 403 on `/branch_protections` (needs owner/admin), so Kai or an admin surface applies this by hand or via `ward ops forgejo` admin verbs. One caveat to time it with: PRs opened before #454 landed will not produce the new context until rebased onto a main that carries the job. Refs: #454, #452, docs/pr-dev-base-build-validation.md.
Author
Owner

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).

This issue carried priority/P4, the icebox tier, meaning it had already been judged parked rather than planned. The burn-down changed what an open issue means: the tracker now holds work that is actually on the list, and the icebox lives in closed state instead of at the bottom of open.

Nothing here was judged wrong or worthless. If this becomes live work, reopen it. The whole set is recoverable with state:closed label:burndown-2026-08.

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901). This issue carried `priority/P4`, the icebox tier, meaning it had already been judged parked rather than planned. The burn-down changed what an open issue means: the tracker now holds work that is actually on the list, and the icebox lives in closed state instead of at the bottom of open. Nothing here was judged wrong or worthless. If this becomes live work, reopen it. The whole set is recoverable with `state:closed label:burndown-2026-08`.
coilyco-ops 2026-08-27 02:57:39 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#457
No description provided.