ceremony/changelog.d/242.md at dac4946e4384c07966ba9f62dbee4b4f89b80f86 - codex-bot-andresmgsl/ceremony - Forgejo: Beyond coding. We Forge.

codex-bot-andresmgsl/ceremony

forked from heavy-duty/ceremony

cndgrr 9c690f02b7 test(issueflow): drive the merge-order selection, and the spent-marker shape end to end

issue_probe's merged-PR argument becomes a spec list — `PR` or `PR@<iso>`
— so a probe can state merge order; the bare form keeps every existing call
site literal.

The direct-drive cases cover crew#176's shape (the lower number merged
later), agreeing orders, interleaved issues, the mergedAt tie broken by
highest PR number under both input orders, and the empty answer. The
end-to-end probe is crew#321's: a marker already standing for the
later-merged, lower-numbered PR must suppress the transition, which
selecting by number could never do.

Two static pins keep the request count honest — the sweep issues exactly two
GraphQL queries, with mergedAt selected on the merged-PR node it already
fetched.

Refs #242

2026-08-03 16:27:43 +00:00

5 lines

241 B

Markdown

Raw Blame History

 ### Fixed
 - The issue-flow sweep now reads an issue's deliverable as the `Refs` PR that
   merged last, not the one numbered highest — merge order is not number order,
   and the old rule spent the transition marker on the wrong PR (#242).