|
| 1 | +# This is a comment. |
| 2 | +# Each line is a file pattern followed by one or more owners. |
| 3 | + |
| 4 | +# These owners will be the default owners for everything in |
| 5 | +# the repo. Unless a later match takes precedence, |
| 6 | +# @kjanat will be requested for |
| 7 | +# review when someone opens a pull request. |
| 8 | +* @kjanat |
| 9 | + |
| 10 | +# Order is important; the last matching pattern takes the most |
| 11 | +# precedence. When someone opens a pull request that only |
| 12 | +# modifies JS files, only @js-owner and not the global |
| 13 | +# owner(s) will be requested for a review. |
| 14 | +# *.js @js-owner # This is an inline comment. |
| 15 | + |
| 16 | +# You can also use email addresses if you prefer. They'll be |
| 17 | +# used to look up users just like we do for commit author |
| 18 | +# emails. |
| 19 | +# *.go docs@example.com |
| 20 | + |
| 21 | +# Teams can be specified as code owners as well. Teams should |
| 22 | +# be identified in the format @org/team-name. Teams must have |
| 23 | +# explicit write access to the repository. In this example, |
| 24 | +# the octocats team in the octo-org organization owns all .txt files. |
| 25 | +# *.txt @octo-org/octocats |
| 26 | + |
| 27 | +# In this example, @doctocat owns any files in the build/logs |
| 28 | +# directory at the root of the repository and any of its |
| 29 | +# subdirectories. |
| 30 | +# /build/logs/ @doctocat |
| 31 | + |
| 32 | +# The `docs/*` pattern will match files like |
| 33 | +# `docs/getting-started.md` but not further nested files like |
| 34 | +# `docs/build-app/troubleshooting.md`. |
| 35 | +# docs/* docs@example.com |
| 36 | + |
| 37 | +# In this example, @octocat owns any file in an apps directory |
| 38 | +# anywhere in your repository. |
| 39 | +# apps/ @octocat |
| 40 | + |
| 41 | +# In this example, @doctocat owns any file in the `/docs` |
| 42 | +# directory in the root of your repository and any of its |
| 43 | +# subdirectories. |
| 44 | +# /docs/ @doctocat |
| 45 | + |
| 46 | +# In this example, any change inside the `/scripts` directory |
| 47 | +# will require approval from @doctocat or @octocat. |
| 48 | +# /scripts/ @doctocat @octocat |
| 49 | + |
| 50 | +# In this example, @octocat owns any file in a `/logs` directory such as |
| 51 | +# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes |
| 52 | +# in a `/logs` directory will require approval from @octocat. |
| 53 | +# **/logs @octocat |
| 54 | + |
| 55 | +# In this example, @octocat owns any file in the `/apps` |
| 56 | +# directory in the root of your repository except for the `/apps/github` |
| 57 | +# subdirectory, as its owners are left empty. Without an owner, changes |
| 58 | +# to `apps/github` can be made with the approval of any user who has |
| 59 | +# write access to the repository. |
| 60 | +# /apps/ @octocat |
| 61 | +# /apps/github |
| 62 | + |
| 63 | +# In this example, @octocat owns any file in the `/apps` |
| 64 | +# directory in the root of your repository except for the `/apps/github` |
| 65 | +# subdirectory, as this subdirectory has its own owner @doctocat |
| 66 | +# /apps/ @octocat |
| 67 | +# /apps/github @doctocat |
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
0 commit comments