Rule: inform people about merge conflict (comment)

• conflict

Rule: automatic merge on CI success for pixel contributions (queue)

• status-success=build
• #files=1
• -conflict
• -draft [:pushpin: queue requirement]
• -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
• files=_data/pixels.json
• any of: [:twisted_rightwards_arrows: queue conditions]
  • all of [:pushpin: queue conditions of queue default]

Rule: automatic merge on CI success for pixel contributions (label)

• status-success=build
• #files=1
• -conflict
• files=_data/pixels.json

Rule: create comment for failed CI (comment, label)

• status-failure=build

Rule: add label for review for more than one file change (comment, label)

• #files>=2

---

💖  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