coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 106 Pull requests 1 Projects Releases 737 Packages Wiki Activity Actions

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
Conversation 0 Commits 1 Files changed 4 +93 -16
coilyco-ops commented 2026-07-15 08:02:23 +00:00
Member
Copy link

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
Details
db5a19a22c 
closes #1344
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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.