Stop committing the upstream Forgejo swagger spec in aos #437
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!437
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-435"
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?
closes #435
ward.workflow: pull-requests-and-merge
WARD-OUTCOME: blocked 🛑
details
workflow: pull-requests-and-merge; review summary: skipped by ~/.ward/config.yaml default Blocker: Forgejo `ci / gate` failed twice on PR #437, each time after `Repo test gate`. Local `ward exec test` and `ward exec pre-commit-all` pass on this tree. The Forgejo job log route returned 404 for runs 918 and 922, so the failing step output is not visible from the run UI. Follow-up: inspect the Forgejo runner or job-log plumbing, or rerun the PR gate once logs are reachable.