@balonik I don’t know how to interact with someone that refuses to read what I wrote. I have no interest in instructions on how to enable/disable self-approve. I already know how to do this, it’s trivial.
However, I want to make it so that approvers who submit merge requests can be approved by anyone.
This is the part I don’t fully understand. If someone is in the list of approvers, all users in the project should be able to approve their merge request. Wouldn’t that be a trust problem when everyone can approve, and not the specified list of approvers? Maybe there is an example that can help understand the requirements better.
Required approvals do take a minimum number into account, but I don’t think that one can be separated between approvers as MR authors (everyone) and everyone (only approvers). Suggest opening a feature proposal to discuss.
An alternative route can be to elect more eligible approvers from multiple groups, and have more broad approval rules so that everyone can review each other. This requires trust and documentation.
I do not want approvers to be able to self-approve.
General thought: I read that the API is being used; understanding and explaining the concepts work better with the main feature documentation in my experience. From there, one can investigate the API endpoints documentation needed to achieve the different steps.