diff --git a/src/content/docs/merge-queue/scopes/bazel.mdx b/src/content/docs/merge-queue/scopes/bazel.mdx index 98090508a4..d142b9dea9 100644 --- a/src/content/docs/merge-queue/scopes/bazel.mdx +++ b/src/content/docs/merge-queue/scopes/bazel.mdx @@ -4,12 +4,18 @@ description: Configure merge queue scopes using Bazel's dependency graph for pre --- import ScopesDetection from '~/components/ScopesDetection.astro'; +import Youtube from '~/components/Youtube.astro'; If you're using monorepo tools like Bazel that have built-in dependency graph analysis, you can use their affected project detection instead of file patterns. This approach is often more accurate because these tools understand your project's dependency relationships. +Here's the whole setup running on a Bazel monorepo, from the `bazel query` step in CI to +several packages testing in their own lanes at once: + + + ## Configuring Manual Scopes To use the manual scopes mechanism, configure Mergify to expect scopes from your CI system: