![]() ![]() * Order is important the last matching pattern takes the most # review when someone opens a pull request. # These owners will be the default owners for everything in # Each line is a file pattern followed by one or more owners. Example of a CODEOWNERS file # This is a comment. For more information, see " Repositories" in the REST API documentation. A list of errors in a repository's CODEOWNERS file is also accessible via the API. When you navigate to the CODEOWNERS file in your repository on, you can see any errors highlighted. If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. Since CODEOWNERS are evaluated by GitHub, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file. For more information about managed user accounts, see " About Enterprise Managed Users" in the GitHub Enterprise Cloud documentation.ĬODEOWNERS paths are case sensitive, because GitHub uses a case sensitive file system. In most cases, you can also refer to a user by an email address that has been added to their account on, for example You cannot use an email address to refer to a managed user account. If the code owners are not on the same line, the pattern matches only the last mentioned code owner. If you want to match two or more code owners with the same pattern, all the code owners must be on the same line. Users and teams must have explicit write access to the repository, even if the team's members already have access. The pattern is followed by one or more GitHub usernames or team names using the standard or format.
0 Comments
Leave a Reply. |