Fix closed-unmerged launched PR reaping #1292

Merged
coilyco-ops merged 2 commits from issue-1007 into main 2026-07-14 19:22:22 +00:00
Member

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:

  • It closes the gap where a closed-unmerged PR path left the carried issue reserved.
  • It keeps the fix on consumer code only.

Checks:

  • Targeted go test on the reaper paths passed before the local scratch exhaustion hit broader linting.
  • ward exec test could not complete in this container because the overlay ran out of temp space.

closes #1007
ward.workflow: pull-request-and-merge

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: - It closes the gap where a closed-unmerged PR path left the carried issue reserved. - It keeps the fix on consumer code only. Checks: - Targeted `go test` on the reaper paths passed before the local scratch exhaustion hit broader linting. - `ward exec test` could not complete in this container because the overlay ran out of temp space. closes #1007 ward.workflow: pull-request-and-merge
Fix closed-unmerged launched PR reaping
Some checks failed
test / test (pull_request) Failing after 1m2s
c7bd5c7d73
Author
Member

PR #1292 failed in Forgejo Actions at golangci-lint after go vet and go test passed. The same scratch-space limit also showed up locally while reproducing the lint stage. Please rerun after the runner scratch cache has room again.

PR #1292 failed in Forgejo Actions at `golangci-lint` after `go vet` and `go test` passed. The same scratch-space limit also showed up locally while reproducing the lint stage. Please rerun after the runner scratch cache has room again.
Refactor closed-unmerged PR reap check
All checks were successful
test / test (pull_request) Successful in 37s
f9508a36e7
Sign in to join this conversation.
No description provided.