mergify-events

Inspect the Mergify activity log for repositories and pull requests as timelines or JSON.

32|11|Updated May 17, 2021
One-click install
npx skills add https://github.com/Mergifyio/mergify-cli --skill mergify-events-mergifyio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mergify-events
Source: https://github.com/Mergifyio/mergify-cli/tree/main/skills/mergify-events
Command: npx skills add https://github.com/Mergifyio/mergify-cli --skill mergify-events-mergifyio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a pull request is dequeued, merged, or otherwise acted on by Mergify, engineers need to reconstruct exactly what happened and when. This Skill queries the Mergify activity log so you can audit queue lifecycles, commands, CI Insights events, and freezes without guessing. ## Core Features & Use Cases - Event timeline browsing: List the ~45 Mergify event types (action.queue., command., ci_insights.*, freezes) for a whole repository or a single pull request, oldest first. - Time-window and type filtering: Control the search window with --since (up to the 90-day retention) and filter with repeatable --type flags. - JSON output for scripting: Emit raw API event objects with --json for jq-based filtering and pipeline integration. - Use Case: A PR was unexpectedly dequeued overnight. Run mergify events --pr 1740 --since 7d to see the full action.queue.enter/checks_start/checks_end/leave sequence and identify whether it left the queue or only had checks retried. ## Quick Start Ask the assistant to show all Mergify events for pull request 1740 over the last 7 days using the mergify events command.

Frequently Asked Questions about mergify-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see what Mergify did to a pull request?

Run mergify events --pr <number> to list that PR's Mergify activity log as a timeline. It covers the last 24 hours by default; add --since 7d or wider (up to 90d) to search further back.

How to filter Mergify events by event type?

Pass the --type flag repeatedly, for example mergify events --type action.queue.leave --type command.queue. With --json, filter the raw events array using jq on .events[].type and .events[].metadata.

Why does mergify events show no events for my pull request?

The default window is only the last 24 hours, so older activity appears empty. Widen the search with --since 90d, which is the maximum retention; the empty-result message always names the exact window searched.

Does action.queue.checks_end mean the PR left the merge queue?

No. An abort code on action.queue.checks_end (such as CHECKS_RETRIED or PR_AHEAD_DEQUEUED) means checks were interrupted while the PR stayed queued. Only action.queue.leave means the PR actually left the queue.

When should I use mergify queue show instead of mergify events?

Use mergify queue show <PR> when asking why a specific PR was dequeued, since it renders the leave reason, failing check job URLs, and staleness checks. Use mergify events for the full event trail or non-queue events.