Fix closed-unmerged launched PR reaping #1292
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
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
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1292
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1007"
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?
This patch teaches the container reaper to notice a launched run whose submitted PR later closes without merging, then comment failure and release the reservation instead of leaving the issue silently stuck.
Why:
Checks:
go teston the reaper paths passed before the local scratch exhaustion hit broader linting.ward exec testcould not complete in this container because the overlay ran out of temp space.closes #1007
ward.workflow: pull-request-and-merge
PR #1292 failed in Forgejo Actions at
golangci-lintaftergo vetandgo testpassed. The same scratch-space limit also showed up locally while reproducing the lint stage. Please rerun after the runner scratch cache has room again.