Greg Dubicki

I would have to check what are the options to restore the default „any eligible dev” approval rule with the API and we should come up with a proposal for...

Thanks for checking! Yes, we definitely would have add some code to support this.

I am beginning working on this feature. For a start I would like to get feedback on a configuration syntax proposal. The current syntax, f.e.: ```yaml merge_requests: approvals: approvals_before_merge: 2...

> Is it more work to support/remove the usage of ids? Personally I don't think I would use the ids, but we seem to support that for advanced branch protection...

> It does sound much more convenient to use group/user/branch names instead of IDs, I've not used the IDs so far though to be honest so I don't have an...

Thanks @weakcamel! I plan to implement this feature over the next few weeks and will release a RC version and I will appreciate testing it. :)

What @zanella is tackling in #423 made me realize that from the implementation point of view it would be easier to treat managing Merge Requests approvals split into: * approvals...

Hey @andrei-abusan, unfortunately none of these things is possible as of now. I believe that setting group visibility would be trivial to add and I can do that. I don't...

Apart from that that you use camel case instead of underscore separator for the `createIfNotPresent` key name, I like your design proposal, thanks. :) However as we don't really need...

So as I was afraid, adding full subgroups support is not so easy. For now I was just going through array of groups and getting their projects. Now I have...