ci(mergify): upgrade configuration to current format

[mergify]

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2026-09-30, otherwise your configuration will stop working.

What's Changed?

• pull_request_rules → actions → merge → commit_message_template: The commit_message_template setting is deprecated. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template (deadline: 2026-09-30)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

• check-success = Configuration changed

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[greptile-apps]

Confidence Score: 3/5

Safe to merge only if the team is comfortable losing the PR number from squash commit message titles going forward.

The migration is not a pure format swap — the old template appended (#{{ number }}) to every squash commit title, but title: pr-title produces only the bare PR title. Future squash commits will no longer carry the PR number, which breaks the commit-to-PR traceability that was baked into the original template. Everything else in the file is unchanged and structurally sound.

.mergify.yml — specifically the commit_message_format block and whether title: pr-title matches the team's intended commit message style.

Important Files Changed

Filename	Overview
.mergify.yml	Replaces deprecated commit_message_template with commit_message_format, but the new title: pr-title omits the PR number that was explicitly included in the old template ({{ title }} (#{{ number }})), changing the squash commit message format.

_{Reviews (1): Last reviewed commit: "ci(mergify): upgrade configuration to cu..." | Re-trigger Greptile}

[greptile-apps]

PR number dropped from squash commit titles

The old template produced titles like Fix some bug (#42) by explicitly appending (#{{ number }}). The new title: pr-title maps to the bare PR title with no number appended, so all future squash commits will silently lose the PR reference. Anyone using git log or git bisect to trace a commit back to a PR will no longer have that link in the message itself. Consider whether title: pr-title-number (if supported) or a custom title template that preserves the number would better match the original intent.