Rule: Ping PR author when conflicting (comment)

• conflict
• -closed

Rule: Ping PR author when title does not follow conventional commits (comment)

• -title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:(.+))?:

Rule: Automatic rebase (merge)

• check-success~=.*Success
• label=auto-rebase
• #review-threads-unresolved=0
• -closed [📌 merge requirement]
• -conflict
• -conflict [📌 merge requirement]
• -draft
• -draft [📌 merge requirement]
• base=master
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: Automatic squash (merge)

• check-success~=.*Success
• label=auto-squash
• #review-threads-unresolved=0
• -closed [📌 merge requirement]
• -conflict
• -conflict [📌 merge requirement]
• -draft
• -draft [📌 merge requirement]
• base=master
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: Delete head branch after merge but not if other PRs depend on it (delete_head_branch)

• closed [📌 delete_head_branch requirement]
• merged

---

💖  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