---
title: Integrating Buildkite with Mergify
description: Run CI Insights, Monorepo CI, and Merge Queue Scopes on Buildkite.
---

<IntegrationLogo src={buildkiteLogo} alt="Buildkite logo"/>

[Buildkite](https://buildkite.com/) is a CI/CD tool with pipeline orchestration
and self-hosted runners. Mergify has native integrations for Buildkite covering
CI Insights, Monorepo CI, and Merge Queue Scopes. Any Buildkite status check
reported to GitHub can also be referenced from your Mergify
[conditions](/configuration/conditions) via `check-success`.

## Prerequisites

1. Buildkite is properly set up and is building your projects. See the
   [Buildkite
   Documentation](https://buildkite.com/docs/tutorials/getting-started) for
   help with setting up Buildkite.

2. Buildkite is [configured to report build statuses to
   GitHub](https://buildkite.com/docs/integrations/github#connecting-buildkite-and-github).

3. The [Mergify GitHub App](/integrations/github) is installed in your repository.

## Mergify features for Buildkite

- **[CI Insights](/ci-insights/setup/buildkite)**: collect Buildkite job
  metrics, detect flaky tests, and get Slack notifications for CI failures.

- **[Monorepo CI](/monorepo-ci/buildkite)**: skip unaffected pipelines on
  pull requests to cut CI spend in monorepos.

- **[Merge Queue Scopes](/merge-queue/scopes/others)**: run only the jobs
  affected by a batch when processing the merge queue. Examples for
  [Bazel](/merge-queue/scopes/bazel),
  [Nx](/merge-queue/scopes/nx), and
  [Turborepo](/merge-queue/scopes/turborepo) are available.