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

Open
opened 2026-07-10 22:07:42 +00:00 by coilyco-ops · 0 comments
Member

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.
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.