Rule: automatic merge for pre-commit ci updates (merge)

• -closed [📌 merge requirement]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• author=pre-commit-ci[bot]
• title=[pre-commit.ci] pre-commit autoupdate
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success = pre-commit.ci - pr
  • check-neutral = pre-commit.ci - pr
  • check-skipped = pre-commit.ci - pr
• any of: [🛡 GitHub branch protection]
  • check-success = main / collector
  • check-neutral = main / collector
  • check-skipped = main / collector
• any of: [🛡 GitHub branch protection]
  • check-success = main-win / collector
  • check-neutral = main-win / collector
  • check-skipped = main-win / collector

---

💖  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