Rule: automatic merge after review (merge)

• #approved-reviews-by>=1
• #approved-reviews-by>=1 [🛡 GitHub branch protection]
• -draft [:pushpin: merge requirement]
• approved-reviews-by=@longhorn/maintainer
• check-success=codespell
• check-success=continuous-integration/drone/pr
• label=ready-to-merge
• any of: [🛡 GitHub branch protection]
  • check-neutral=continuous-integration/drone/pr
  • check-skipped=continuous-integration/drone/pr
  • check-success=continuous-integration/drone/pr
• #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
• -conflict [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• check-success=CodeFactor
• check-success=DCO
• any of: [🛡 GitHub branch protection]
  • check-success=DCO
  • check-neutral=DCO
  • check-skipped=DCO

Rule: ask to resolve conflict (comment)

• conflict

Rule: backport patches to stable branch (backport)

• merged [:pushpin: backport requirement]
• base=master

---

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

🚀  You can help us by becoming a sponsor!

---

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