fix(promote): align repo gate with ci #569
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
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!569
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-568"
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?
Promote was branching onto
ward exec testin the release container, which diverged from the passingci.ymlgate. This change makes promote run the same direct repo gate as CI and pins the workflow shape with a regression test..forgejo/workflows/promote.ymlwithuv run pytestandpre-commit run --all-files.ward exec test,ward exec pre-commit-all.closes #568
ward.workflow: pull-request-and-merge
coilyco-ops referenced this pull request2026-07-15 08:17:57 +00:00
WARDED_WORKFLOW: #569
details
workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) felt: small and mechanical. The fix was workflow parity, not a code-path chase. confidence: high surprises: the PR CI settled cleanly once promote stopped preferring ward. follow-ups: noneWARDED_WORKFLOW: #569
details
workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) felt: small and mechanical. The fix was workflow parity, not a code-path chase. confidence: high surprises: the PR CI settled cleanly once promote stopped preferring ward. follow-ups: noneWARDED_WORKFLOW: #569
details
workflow: pull-request-and-merge; review summary: passed felt: small and mechanical. The fix was workflow parity, not a code-path chase. confidence: high surprises: the PR CI settled cleanly once promote stopped preferring ward. follow-ups: none