Rule: Auto-Merge on Approving Label and Changes Limited to docs/ Folder (merge)

• #approved-reviews-by>=1 [🛡 GitHub branch protection]
• -files~=^(?!^docs).*
• branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
• files~=^docs/
• label=doc-merge
• any of: [🛡 GitHub branch protection]
  • check-neutral=DCO
  • check-skipped=DCO
  • check-success=DCO
• any of: [🛡 GitHub branch protection]
  • check-neutral=FVT Tests
  • check-skipped=FVT Tests
  • check-success=FVT Tests
• any of: [🛡 GitHub branch protection]
  • check-neutral=Verify Build
  • check-skipped=Verify Build
  • check-success=Verify Build
• #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
• -closed [📌 merge requirement]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed

---

💖  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