✅ Rule: label changes from community (label)

• author≠@core-contributors
• author≠@monorepo-maintainers
• author≠@monorepo-triage
• author≠@monorepo-write
• author≠dependabot[bot]
• author≠github-actions[bot]
• author≠mergify[bot]

Rule: request review for community changes (request_reviews)

• #commented-reviews-by=0
• #approved-reviews-by=0
• #changes-requested-reviews-by=0
• #review-requested=0
• author≠@core-contributors
• author≠@monorepo-maintainers
• author≠@monorepo-triage
• author≠@monorepo-write
• author≠dependabot[bot]
• author≠github-actions[bot]
• author≠mergify[bot]

Rule: automatic merge (squash) on CI success (merge)

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
• -closed [📌 merge requirement]
• all of:
  • label=automerge
  • status-success=buildkite/solana
  • status-success=ci-gate
  • any of:
    • -files~=^docs/
    • status-success=build & deploy docs
  • label!=no-automerge
  • any of:
    • -files~=(\.rs|Cargo\.toml|Cargo\.lock|\.github/scripts/cargo-clippy-before-script\.sh|\.github/workflows/cargo\.yml)$
    • all of:
      • any of:
        • check-success=clippy-stable (macos-latest)
        • check-success=clippy-stable (macos-latest-large)
      • any of:
        • check-success=clippy-nightly (macos-latest)
        • check-success=clippy-nightly (macos-latest-large)
  • any of:
    • -files~=(\.rs|Cargo\.toml|Cargo\.lock|cargo-build-bpf|cargo-test-bpf|cargo-build-sbf|cargo-test-sbf|ci/downstream-projects/run-spl\.sh|\.github/workflows/downstream-project-spl\.yml)$
    • all of:
      • status-success=cargo-test-sbf (associated-token-account/program, associated-token-account/program-test)
      • status-success=cargo-test-sbf (feature-proposal/program)
      • status-success=cargo-test-sbf (governance/addin-mock/program, governance/program)
      • status-success=cargo-test-sbf (instruction-padding/program, token/program-2022, token/program-2022-test)
      • status-success=cargo-test-sbf (memo/program)
      • status-success=cargo-test-sbf (name-service/program)
      • status-success=cargo-test-sbf (single-pool/program)
      • status-success=cargo-test-sbf (stake-pool/program)
      • status-success=cargo-test-sbf (token-upgrade/program)
      • status-success=cargo-test-sbf (token/program)
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: remove automerge label on CI failure (comment, label)

• all of:
  • #status-failure!=0
  • label=automerge
  • -merged

Rule: v1.17 feature-gate backport (backport)

• label=feature-gate
• label=v1.17
• merged [📌 backport requirement]

Rule: v1.17 non-feature-gate backport (backport)

• label=v1.17
• merged [📌 backport requirement]
• label!=feature-gate

Rule: v1.17 backport warning comment (comment)

• label=v1.17

Rule: v1.18 feature-gate backport (backport)

• label=feature-gate
• label=v1.18
• merged [📌 backport requirement]

Rule: v1.18 non-feature-gate backport (backport)

• label=v1.18
• merged [📌 backport requirement]
• label!=feature-gate

Rule: v1.18 backport warning comment (comment)

• label=v1.18

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

1 not applicable rule

Rule: label changes from monorepo-triage (label)

• author=@monorepo-triage
• author≠@core-contributors
• author≠@monorepo-maintainers
• author≠@monorepo-write
• author≠dependabot[bot]
• author≠github-actions[bot]
• author≠mergify[bot]

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com