Skip to content

docs: verify a dropped merge-queue entry via the issue timeline before re-arming #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CybotTM merged 2 commits into from
Jul 16, 2026
+18 −0
Merged

docs: verify a dropped merge-queue entry via the issue timeline before re-arming #99

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
047ffd2
docs: verify a dropped queue entry via the issue timeline before re-a…
CybotTM Jul 16, 2026
605be5c
docs: simplify the timeline jq recipe (IN(), optional iteration)
CybotTM Jul 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions skills/git-workflow/references/pull-request-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -907,6 +907,24 @@ gh api graphql -F id="$PRID" \
# Branch is pushable again; fix threads, then re-arm through this gate.
```

**Verify a "dropped" queue entry via the issue timeline before re-arming.**
Right after a queue merge, `gh pr view --json state` can report `OPEN` and the
queue listing can show the entry gone for several minutes — the exact signature
of a silent drop, except the PR already merged. Re-arming (or re-diagnosing) on
that stale read wastes a round-trip. The issue **timeline** is authoritative:

```bash
gh api repos/{owner}/{repo}/issues/NUMBER/timeline --paginate \
--jq '.[]? | select(.event | IN("added_to_merge_queue", "removed_from_merge_queue",
"merged", "closed")) | "\(.created_at) \(.event)"'
# removed_from_merge_queue immediately followed by merged -> it landed; do nothing.
# removed_from_merge_queue with NO merged event -> real silent drop; re-arm.
```

Also note: queue membership is GraphQL-only — `isInMergeQueue` /
`mergeQueueEntry` are **not** `gh pr view --json` fields (the call errors);
query `pullRequest { mergeQueueEntry { state position } }` via `gh api graphql`.

### Signing Readiness (Preflight — Before Committing)

A signing failure surfaces only at the *merge gate* (BLOCKED on DCO / "verified signatures") — i.e. **after** all the work is staged, forcing a full re-sign cycle. Catch it up front: before a commit-heavy run (e.g. `/pr-finish`), confirm a signing key is actually available and that `git commit -S` will sign, rather than assuming it.
Expand Down
Loading