ci: make base Mergify policy valid - #320
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 150d08f13c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| merge: | ||
| method: squash | ||
|
|
||
| # Add reviewers based on changed paths |
There was a problem hiding this comment.
Restore valid bot auto-merge coverage
With the bot-specific merge rules removed here, Dependabot/Renovate PRs now fall through to the only remaining merge rule, which requires #approved-reviews-by>=1; renovate.json still enables automerge for non-major, manager-specific, GitHub Actions, Docker, and vulnerability updates, but main is protected by a required reviewer, so those PRs will sit until human approval instead of merging automatically. Please keep valid bot-specific rules, e.g. split the author cases into separate rules or add an explicit bot approval path, rather than deleting the automation entirely.
Useful? React with 👍 / 👎.



Removes unsupported Mergify actions and conditions from the default branch configuration: post_merge, author OR expressions, age-based stale closure, and github_accounts. Retains explicit review, merge, labeling, and warning rules. This is a base-policy fix required before dependent foundation PRs can receive valid Mergify Merge Queue/Summary evaluations.