post_merge_pr_for_issue answered "which merged Refs PR is this issue's deliverable?" with sort -n | tail -n1. Merge order is not number order: crew#176's two Refs PRs merged #184 at 19:05:16Z and #182 at 19:05:18Z. MERGED_REF_PR_RECORDS gains mergedAt as a third column — a field on the merged-PR node set already fetched, so no additional GraphQL request — and the selection sorts on it, breaking ties by highest PR number so the answer never depends on input order. Refs #242 |
||
|---|---|---|
| .. | ||
| changelog-armed | ||
| changelog-assembled | ||
| changelog-monotonic | ||
| docs-sync | ||
| drill-recorded | ||
| issueflow-reconcile | ||
| labels-reconcile | ||
| labels-scope | ||
| runner-isolated | ||
| .gitkeep | ||