View as Markdown

Integrating GitHub Actions with Mergify

Run CI Insights, Monorepo CI, and Merge Queue Scopes on GitHub Actions, and trigger workflows from Mergify rules.

GitHub Actions is the CI/CD platform provided by GitHub. Mergify has native integrations for GitHub Actions covering CI Insights, Monorepo CI, and Merge Queue Scopes, and can trigger workflows directly from a rule. Any GitHub Actions job status can also be referenced from your Mergify conditions via check-success.

Prerequisites

Section titled Prerequisites

  1. You’ve set up GitHub Actions in your repository. If you’re new to GitHub Actions, their official documentation provides comprehensive guides.

  2. GitHub Actions is already configured to report job statuses to your pull requests.

  3. The Mergify GitHub App is installed in your repository.

Mergify features for GitHub Actions

Section titled Mergify features for GitHub Actions

  • CI Insights: collect job metrics, detect flaky tests, and get Slack notifications for CI failures.

  • Monorepo CI: skip unaffected jobs on pull requests to cut CI spend in monorepos.

  • Merge Queue Scopes: run only the jobs affected by a batch when processing the merge queue. Examples for Bazel, Nx, and Turborepo are available.

  • github_actions action: trigger a workflow directly from a Mergify rule.

Was this page helpful?

Edit this page on GitHub