fix(autopilot): harden Repo2 deployment configuration and execution - #278

commit_message_template is deprecated and will be removed on 2026-09-30. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template

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

• #review-threads-unresolved=0
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue rule default]
    • #review-threads-unresolved=0
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by=0
    • -label~=(do-not-merge)
    • github-review-approved [🛡 GitHub branch protection]
    • status-success=build
    • status-success=dependency-review
    • any of: [🛡 GitHub branch protection]
      • check-success = build
      • check-neutral = build
      • check-skipped = build
• #approved-reviews-by>=1
• #changes-requested-reviews-by=0
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• -label~=(do-not-merge)
• status-success=build
• status-success=dependency-review
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted

---

💖  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