|
| 1 | +# NHS Notify Code Owners |
| 2 | + |
| 3 | +# Notify default owners |
| 4 | +* @NHSDigital/nhs-notify-repository-template |
| 5 | + |
| 6 | +/.github/ @NHSDigital/nhs-notify-repository-template-admins |
| 7 | +*.code-workspace @NHSDigital/nhs-notify-repository-template-admins |
| 8 | +/infrastructure/terraform/ @NHSDigital/nhs-notify-platform |
| 9 | + |
| 10 | +# Codeowners must be final check |
| 11 | +/.github/CODEOWNERS @NHSDigital/nhs-notify-code-owners |
| 12 | +/CODEOWNERS @NHSDigital/nhs-notify-code-owners |
| 13 | + |
| 14 | + |
| 15 | +# Each NHS Notify repository should have clear code owners set. |
| 16 | +# Do not use GitHub team names, instead use the GitHub usernames |
| 17 | +# of the people who are responsible for the code maintenance. |
| 18 | + |
| 19 | +# This is a comment. |
| 20 | +# Each line is a file pattern followed by one or more owners. |
| 21 | + |
| 22 | +# These owners will be the default owners for everything in |
| 23 | +# the repo. Unless a later match takes precedence, |
| 24 | +# @global-owner1 and @global-owner2 will be requested for |
| 25 | +# review when someone opens a pull request. |
| 26 | +# * @global-owner1 @global-owner2 |
| 27 | + |
| 28 | +# Order is important; the last matching pattern takes the most |
| 29 | +# precedence. When someone opens a pull request that only |
| 30 | +# modifies JS files, only @js-owner and not the global |
| 31 | +# owner(s) will be requested for a review. |
| 32 | +# *.js @js-owner #This is an inline comment. |
| 33 | + |
| 34 | +# You can also use email addresses if you prefer. They'll be |
| 35 | +# used to look up users just like we do for commit author |
| 36 | +# emails. |
| 37 | + |
| 38 | + |
| 39 | +# Teams can be specified as code owners as well. Teams should |
| 40 | +# be identified in the format @org/team-name. Teams must have |
| 41 | +# explicit write access to the repository. In this example, |
| 42 | +# the octocats team in the octo-org organization owns all .txt files. |
| 43 | +# *.txt @octo-org/octocats |
| 44 | + |
| 45 | +# In this example, @doctocat owns any files in the build/logs |
| 46 | +# directory at the root of the repository and any of its |
| 47 | +# subdirectories. |
| 48 | +# /build/logs/ @doctocat |
| 49 | + |
| 50 | +# The `docs/*` pattern will match files like |
| 51 | +# `docs/getting-started.md` but not further nested files like |
| 52 | +# `docs/build-app/troubleshooting.md`. |
| 53 | + |
| 54 | + |
| 55 | +# In this example, @octocat owns any file in an apps directory |
| 56 | +# anywhere in your repository. |
| 57 | +# apps/ @octocat |
| 58 | + |
| 59 | +# In this example, @doctocat owns any file in the `/docs` |
| 60 | +# directory in the root of your repository and any of its |
| 61 | +# subdirectories. |
| 62 | +# /docs/ @doctocat |
| 63 | + |
| 64 | +# In this example, any change inside the `/scripts` directory |
| 65 | +# will require approval from @doctocat or @octocat. |
| 66 | +# /scripts/ @doctocat @octocat |
| 67 | + |
| 68 | +# In this example, @octocat owns any file in a `/logs` directory such as |
| 69 | +# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes |
| 70 | +# in a `/logs` directory will require approval from @octocat. |
| 71 | +# **/logs @octocat |
| 72 | + |
| 73 | +# In this example, @octocat owns any file in the `/apps` |
| 74 | +# directory in the root of your repository except for the `/apps/github` |
| 75 | +# subdirectory, as its owners are left empty. |
| 76 | +# /apps/ @octocat |
| 77 | +# /apps/github |
| 78 | + |
| 79 | +# In this example, @octocat owns any file in the `/apps` |
| 80 | +# directory in the root of your repository except for the `/apps/github` |
| 81 | +# subdirectory, as this subdirectory has its own owner @doctocat |
| 82 | +# /apps/ @octocat |
| 83 | +# /apps/github @doctocat |
0 commit comments