Manage CODEOWNER groups without being a member of that group
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
When using groups as a codeowners, there is no way that Maintainers/Owners manage the members of that group. Sometimes people are out of the office, personal time off, or for any other reason are not being able to approve/review the Merge Request during a certain period of time, therefore a significant blockage is preventing the process to move forward. If this situation comes up, as a workaround we could add other temporary person to that codeowner group who approves/reviews the changes meanwhile the codeowner comes back.
Additionally, if the codeowner who is on PTO belongs to more than one codeowner group, there is no way for Maintainers/Owners to determine all the groups that person belongs to.
Problem to solve
- If codeowners are not being able to approve/review Merge Requests due to their absence, the process gets stuck because Maintainers/Owners cannot modify the codeowners group they belong in order to add another person to temporarily backup the main codeowner.
- Maintainers/Owners do not have a comprehensive coverage about all the codeowner groups that a person belongs to.
Proposal
- Maintainers/Owners could edit the members of codeowner groups for adding/removing users that for some reason are not being able to review/approve any Merge Request during a certain period of time.
- Maintainers/Owners could propagate the temporary change of adding/removing a person to all groups where a codeowner belongs to.
Intended users
This change is mainly focused for team managers who need a temporary person to approve/review Merge Requests on behalf of people who are temporarily out of the office.
Feature Usage Metrics
The whole Merge Request process does not get stuck when any of the codeowners is not being able to review/approve the code for a certain period of time.
Does this feature require an audit event?
No