Add shared Mergify config

[stasimus]

Central Mergify config for the Scala repos that use the shared CI workflow, so each one only needs extends: scala-github-actions in its own file. Merge queue with rebase, queues approved PRs and scala-steward updates once the test / checks and the AI policy check pass. Asked for in evolution-gaming/scache#393.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 78f84b8a-b472-4588-80fd-47a0fd4ad764

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mr-git]

How this .mergify.yml will work? Should it be referenced somehow in downstream repos? Will it get applied auto-magically after/when we will reference the revision where this change is merged?

[mr-git]

We have to provide some docs on why we added the Mergify integration and how to adjust it in case if config diverges...

[stasimus]

We have to provide some docs on why we added the Mergify integration and how to adjust it in case if config diverges...

I think this is overkill,

1. https://docs.mergify.com/
2. I will add a few notes on local implementation details

[stasimus]

Should it be referenced somehow in downstream repos? Will it get applied auto-magically after/when we will reference the revision where this change is merged?

One line per repo, extends: scala-github-actions, no revision. There is no @sha for extends, so this file goes live for every repo extending it the moment it lands on the default branch. First one is evolution-gaming/scache#393.

The app also has to be installed here, not just downstream, and nesting isn't allowed, so this file can't extend anything itself.

Notes added in bad9656.