Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Note case-sensitivity in CODEOWNERS file
  • Loading branch information
chrisgarber authored Jan 4, 2022
commit 5df1f7e957d7e7e1729872e08f6579afa27e2a49
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,8 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to
A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `[email protected]`.

If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.

CODEOWNERS paths are case sensitive, because GitHub uses a case sensitive file system. Since CODEOWNERS are evaluated by GitHub, even systems (e.g. MacOS) that are case insensitive should ensure that paths and files are cased correctly in the CODEOWNERS file.
### Example of a CODEOWNERS file
```
# This is a comment.
Expand Down