Prevent replacement PR bodies from closing their own PR number instead of the carried issue #1348

Merged
coilyco-ops merged 1 commit from issue-1344 into main 2026-07-15 08:03:34 +00:00
Owner

This fixes the PR-body generation path for replacement PRs so the carried issue number, not the PR number, is used when emitting close trailers. It also adds a recovery note for the already-merged case where the carried issue stayed open, so operators get a direct repair path instead of a silent no-op.

  • What changed: PR continuations now keep the PR identity for display but close the carried issue in the prompt/body path.
  • Why: replacement PRs can have a different PR number than the issue they carry, and the wrong trailer leaves the issue open.
  • Tests: go test ./...

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

This fixes the PR-body generation path for replacement PRs so the carried issue number, not the PR number, is used when emitting close trailers. It also adds a recovery note for the already-merged case where the carried issue stayed open, so operators get a direct repair path instead of a silent no-op. - What changed: PR continuations now keep the PR identity for display but close the carried issue in the prompt/body path. - Why: replacement PRs can have a different PR number than the issue they carry, and the wrong trailer leaves the issue open. - Tests: `go test ./...` closes #1344 ward.workflow: pull-request-and-merge
Fix carried issue trailers for replacement PRs
All checks were successful
test / test (pull_request) Successful in 44s
db5a19a22c
closes #1344
Commenting is not possible because the repository is archived.
No reviewers
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward!1348
No description provided.