[TOC] ## 概述 - GitHub 和 GitLab 都支持這一特性 - 使用CODEOWNERS文件來指定負責存儲庫中某些文件的用戶或共享組 - 當有人提交 pull request 或 push 代碼到受保護的分支時，代碼所有者會自動被要求進行審查 ## gitlab 流程 > [參考](http://www.hmoore.net/apachecn/gitlab-doc-zh/1948642) 1. 您可以在三個位置選擇并添加CODEOWNERS文件： ``` 到存儲庫的根目錄 在.gitlab/目錄中 在docs/目錄中 ``` 沖突時,以下方為主 ``` README.md @user1 # This line would also match the file README.md *.md @user2 ``` 將顯示README.md的用戶為@user2 . 2. Approvals by Code Owners 將"代碼所有者"設置為項目后，可以將其配置為用于合并請求批準： * As[merge request eligible approvers](http://www.hmoore.net/apachecn/gitlab-doc-zh/merge_requests/merge_request_approvals.html#code-owners-as-eligible-approvers). * 根據需要批準[分支機構](http://www.hmoore.net/apachecn/gitlab-doc-zh/protected_branches.html#protected-branches-approval-by-code-owners-premium). **注意**：為了批準合并請求，需要開發人員或更高[權限](http://www.hmoore.net/apachecn/permissions.html). 設置后，"代碼所有者"將顯示在合并請求小部件中：  3. CODEOWNERS 文件的語法 可以使用與.gitignore文件中使用的相同類型的模式來指定文件，然后使用一個或多個用戶的@username或電子郵件或應作為文件所有者的一個或多個組的@name進行指定. 必須將組添加為項目的成員 ，否則它們將被忽略 <details> <summary> CODEOWNERS</summary> ``` # This is an example of a code owners file # lines starting with a `#` will be ignored. # app/ @commented-rule # We can specify a default match using wildcards: * @default-codeowner # We can also specify "multiple tab or space" separated codeowners: * @multiple @code @owners # Rules defined later in the file take precedence over the rules # defined before. # This will match all files for which the file name ends in `.rb` *.rb @ruby-owner # Files with a `#` can still be accessed by escaping the pound sign \#file_with_pound.rb @owner-file-with-pound # Multiple codeowners can be specified, separated by spaces or tabs # In the following case the CODEOWNERS file from the root of the repo # has 3 code owners (@multiple @code @owners) CODEOWNERS @multiple @code @owners # Both usernames or email addresses can be used to match # users. Everything else will be ignored. For example this will # specify `@legal` and a user with email `janedoe@gitlab.com` as the # owner for the LICENSE file LICENSE @legal this_does_not_match janedoe@gitlab.com # Group names can be used to match groups and nested groups to specify # them as owners for a file README @group @group/with-nested/subgroup # Ending a path in a `/` will specify the code owners for every file # nested in that directory, on any level /docs/ @all-docs # Ending a path in `/*` will specify code owners for every file in # that directory, but not nested deeper. This will match # `docs/index.md` but not `docs/projects/index.md` /docs/* @root-docs # This will make a `lib` directory nested anywhere in the repository # match lib/ @lib-owner # This will only match a `config` directory in the root of the # repository /config/ @config-owner # If the path contains spaces, these need to be escaped like this: path\ with\ spaces/ @space-owner ``` </details> <br />