-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review Mergify rules #24
Comments
So far I got this done in: Already in place for Lagom and Play:
Side projects.
I didn't touch the community driven repos. I didn't touch playframework/play-generated-docs either because we don't usually send PRs to this one. |
Add mergify on lagom projects: Added mergify on Lagom projects. Most of them will get a slight different mergify file when they got managed by Template Control
|
No remaining issues. |
Well there's #61, but let's close this aggregating issue. |
We have discussed a few options for Mergify rules and here is what I remember so far. Feel free to add/modify it.
Framework / Library Projects
squash only when label present(edit: squash by default, use label to opt-out 👇)dismiss merge label on PR updaterequire at least 2 approvals (???) - I don't remember the decision on thisSample Projects (Template Control rules)
The text was updated successfully, but these errors were encountered: