Approval rule Security All files A security team member reviews all changes for vulnerabilities. The correct set of reviewers, such as frontend developers or a security team.įor example: Type Name Scope Comment Approval rule UX All files A user experience (UX) team member reviews the user experience of all changes made in your project. Approval rules help guide merge request creators to Use Approval rules to define areas of expertise that don’t correspond to specificįile paths in your repository.Define the users who have domain expertise Use Code Owners in combination with merge requestĪpproval rules (either optional or required) Code Owner names are displayed on the files and directories they own:
Combine protected branches with Code Owners to requireĮxperts to approve merge requests before they merge into a protected branch.
Use the Code Owners feature to define who has expertise for specific parts of your project’s codebase.ĭefine the owners of files and directories in a repository to:
0 kommentar(er)
