Identifying, and marking an MR as requiring domain expertise
Some MRs require domain expertise. Maintainers when they receive an MR need to know:
- If this MR requires domain expertise, or not
- Has this MR been reviewed by a domain expert, or not.
I think it defers from area to area. For example:
- grouppipeline execution MRs do require CI maintainers.
- ~"group::authentication and authorization" just requires auth reviewers. Because of a security issue, we now use CODEOWNERS to enforce this
- ~"group::product intelligence" uses Dangerfiles +
changes
- groupcompliance required this starting from !91597 (merged)
Proposal
Use CODEOWNERS required approvals
Edited by Thong Kuah