mergify-merge-queue

Post the comment `@mergifyio queue` on the pull request; Mergify acknowledges it with a thumbs-up reaction. To remove it, comment `@mergifyio dequeue`. There is no CLI subcommand for queuing or dequeuing individual PRs.

Run `mergify queue show <PR_NUMBER>`; it prints the dequeue code, the reason, and failing checks with direct CI job-log URLs. If the CLI cannot read the activity log, fall back to the Mergify Merge Queue check run or the `# Merge Queue Status` bot comment.

CHECKS_FAILED means required checks failed on the temporary merge commit the queue created. Read the failing check's details_url to open the CI job log, fix the failure, then requeue with `@mergifyio queue`; flaky failures can be requeued as-is.

That notice means no queue activity exists in the retained 90-day window: the PR was never queued, its events aged out, or the number is wrong. Confirm the PR exists with `gh pr view` before concluding it was never queued.

Run `mergify queue pause --reason "your reason"` to halt new merges; running CI is not cancelled. Resume with `mergify queue unpause`, and use `--yes-i-am-sure` to skip confirmation in scripts.

The activity log retains 90 days of events, and API queries cannot span more than 93 days. Always pass `received_from` when querying the logs endpoint directly, since the default window is only the last 24 hours.