-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Path based reviews #147
Comments
This is the right place and an excellent idea. |
I think we already support that. In https://doc.mergify.io/configuration.html#required-reviews Can you check it does what you want ? |
I tried it today and unfortunately it does not quite what I need because of this:
Which kind of renders the whole idea useless because I want the mergify bot to merge stuff 😄 |
Any news here? :) |
This doesn't seem to exist anymore, is this feature still supported? |
Hi, not sure if this is the right place to ask or propose this idea but what would be really great is if you could automatically merge PRs that only affect changed files of a certain path.
The use case would be something like a central repository that is used for meta data such as for example Symfony's recipes contrib repo (https://github.com/symfony/recipes-contrib).
There are loads of recipes for all kinds of different vendors and everybody is allowed to add PRs but you cannot grant 500 people push access but rather just want them to review and approve PRs that affect e.g. their own vendor path.
That's why it would be awesome if you could configure people that are sort of "owner" of a given path so that even though these users do not have push access to the repo, they can trigger mergify by approving the PR.
So something like
Not sure if you understand what I'm talking about 😄
The text was updated successfully, but these errors were encountered: