‼️ Action Required ‼️

The configuration uses the deprecated commit_message_template attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: Automatic merge on approval and successful build (delete_head_branch)

• #approved-reviews-by>=1
• closed [📌 delete_head_branch requirement]
• status-success=build
• status-success=package-js
• -label~=(do-not-merge)

Rule: Automatic merge on approval and successful build (queue)

• #approved-reviews-by>=1
• status-success=build
• status-success=package-js
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build
      • check-skipped = build
      • check-success = build
    • any of: [🛡 GitHub branch protection]
      • check-neutral = Validate PR title
      • check-skipped = Validate PR title
      • check-success = Validate PR title
    • any of: [🛡 GitHub branch protection]
      • check-skipped = package-js
      • check-neutral = package-js
      • check-success = package-js
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• -label~=(do-not-merge)
• any of: [📌 queue -> configuration change requirements]
  • check-success = Configuration changed
  • -mergify-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