Events

Browse the events Mergify recorded for the repository

mergify events #

Browse the events Mergify recorded for the repository. List the activity log as a timeline — queue enters and leaves, merges, commands, CI Insights, every event type — for the whole repository or one pull request (--pr). The output always states the time window it covers: the last 24 hours by default, up to the 90 days the log retains (--since 90d).

Usage 
mergify events [OPTIONS]
Options
-t, --token <TOKEN> string

Mergify or GitHub token. Falls back to MERGIFY_TOKEN and then GITHUB_TOKEN env vars

-u, --api-url <API_URL> string

Mergify API URL. Falls back to MERGIFY_API_URL env var, then to the default

-r, --repository <REPOSITORY> string

Repository full name (owner/repo). Falls back to GITHUB_REPOSITORY env var

--pr <PR_NUMBER> string

Only events for this pull request; omit to cover the whole repository

--since <DURATION> string

How far back to look: an integer with a unit — s, m, h, d or w (e.g. 30m, 12h, 7d). Defaults to 24h; the log retains 90 days (--since 90d is the widest useful window). The window always ends now and is stated in the output

--type <EVENT_TYPE> string

Only events of this type (e.g. action.queue.leave). Repeat the flag to match several types; values pass to the API verbatim, so types newer than this CLI work too

--limit <N> string

Stop after the newest N events instead of fetching the whole window. The output says so when it takes effect

--json flag

Emit a single JSON document (the raw events, newest first, with the queried window echoed) instead of the timeline

Global options
-v, --verbose flag

Increase log verbosity: -v info, -vv debug, -vvv trace. Logs go to stderr so stdout stays clean for piping. RUST_LOG overrides this

--debug flag

Shorthand for at least debug-level logging (like -vv)

--color <COLOR> auto | always | never

When to use color in terminal output

Values: auto always never

Default: auto

Was this page helpful?