You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using multi-gitter in a shared environment with the reviewers setting including all members of the team and max-reviewers set to one. However, the MR that is created will include the committer as one of the randomized assignees, and our policy is that committers can't approve their own changes.
Is there a configuration trick to force the randomizer to exclude the person making the commit from the reviewer selection?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're using multi-gitter in a shared environment with the
reviewers
setting including all members of the team andmax-reviewers
set to one. However, the MR that is created will include the committer as one of the randomized assignees, and our policy is that committers can't approve their own changes.Is there a configuration trick to force the randomizer to exclude the person making the commit from the reviewer selection?
Beta Was this translation helpful? Give feedback.
All reactions