Require the ci / build-dev-base status context in branch protection #457
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from #454 / PR #456, which added a
build-dev-basejob to ci.yml: every pull request now builds the whole dev-base tier family build-only through the sharedactions/dev-base-buildcomposite. The remaining step is admin-side: addci / build-dev-baseto the required status contexts in this repo's branch protection, alongside the existingci / 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 viaward ops forgejoadmin 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.