generated from NHSDigital/nhs-notify-repository-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3 from NHSDigital/code-owners
Added code owners to dns repo.
- Loading branch information
Showing
2 changed files
with
119 additions
and
0 deletions.
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
# NHS Notify Code Owners | ||
|
||
* @rossbugginsnhs @m-houston @edmundcraske2-nhs @timireland | ||
|
||
# Default protection for codeowners, must be last in file. | ||
/.github/CODEOWNERS @NHSDigital/nhs-notify-code-owners | ||
/CODEOWNERS @NHSDigital/nhs-notify-code-owners | ||
|
||
|
||
# Each NHS Notify repository should have clear code owners set. | ||
# Do not use GitHub team names, instead use the GitHub usernames | ||
# of the people who are responsible for the code maintenance. | ||
|
||
# This is a comment. | ||
# Each line is a file pattern followed by one or more owners. | ||
|
||
# These owners will be the default owners for everything in | ||
# the repo. Unless a later match takes precedence, | ||
# @global-owner1 and @global-owner2 will be requested for | ||
# review when someone opens a pull request. | ||
# * @global-owner1 @global-owner2 | ||
|
||
# Order is important; the last matching pattern takes the most | ||
# precedence. When someone opens a pull request that only | ||
# modifies JS files, only @js-owner and not the global | ||
# owner(s) will be requested for a review. | ||
# *.js @js-owner #This is an inline comment. | ||
|
||
# You can also use email addresses if you prefer. They'll be | ||
# used to look up users just like we do for commit author | ||
# emails. | ||
# *.go [email protected] | ||
|
||
# Teams can be specified as code owners as well. Teams should | ||
# be identified in the format @org/team-name. Teams must have | ||
# explicit write access to the repository. In this example, | ||
# the octocats team in the octo-org organization owns all .txt files. | ||
# *.txt @octo-org/octocats | ||
|
||
# In this example, @doctocat owns any files in the build/logs | ||
# directory at the root of the repository and any of its | ||
# subdirectories. | ||
# /build/logs/ @doctocat | ||
|
||
# The `docs/*` pattern will match files like | ||
# `docs/getting-started.md` but not further nested files like | ||
# `docs/build-app/troubleshooting.md`. | ||
# docs/* [email protected] | ||
|
||
# In this example, @octocat owns any file in an apps directory | ||
# anywhere in your repository. | ||
# apps/ @octocat | ||
|
||
# In this example, @doctocat owns any file in the `/docs` | ||
# directory in the root of your repository and any of its | ||
# subdirectories. | ||
# /docs/ @doctocat | ||
|
||
# In this example, any change inside the `/scripts` directory | ||
# will require approval from @doctocat or @octocat. | ||
# /scripts/ @doctocat @octocat | ||
|
||
# In this example, @octocat owns any file in a `/logs` directory such as | ||
# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes | ||
# in a `/logs` directory will require approval from @octocat. | ||
# **/logs @octocat | ||
|
||
# In this example, @octocat owns any file in the `/apps` | ||
# directory in the root of your repository except for the `/apps/github` | ||
# subdirectory, as its owners are left empty. | ||
# /apps/ @octocat | ||
# /apps/github | ||
|
||
# In this example, @octocat owns any file in the `/apps` | ||
# directory in the root of your repository except for the `/apps/github` | ||
# subdirectory, as this subdirectory has its own owner @doctocat | ||
# /apps/ @octocat | ||
# /apps/github @doctocat |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Ignore the lock file as this is just an example | ||
.terraform.lock.hcl | ||
# Ignore Terraform plan | ||
*tfplan* | ||
|
||
# SEE: https://github.com/github/gitignore/blob/main/Terraform.gitignore | ||
|
||
# Local .terraform directories | ||
**/.terraform/* | ||
|
||
# .tfstate files | ||
*.tfstate | ||
*.tfstate.* | ||
|
||
# Crash log files | ||
crash.log | ||
crash.*.log | ||
|
||
# Exclude all .tfvars files, which are likely to contain sensitive data, such as | ||
# password, private keys, and other secrets. These should not be part of version | ||
# control as they are data points which are potentially sensitive and subject | ||
# to change depending on the environment. | ||
*.tfvars | ||
*.tfvars.json | ||
|
||
# Ignore override files as they are usually used to override resources locally and so | ||
# are not checked in | ||
override.tf | ||
override.tf.json | ||
*_override.tf | ||
*_override.tf.json | ||
|
||
# Include override files you do wish to add to version control using negated pattern | ||
# !example_override.tf | ||
|
||
# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan | ||
# example: *tfplan* | ||
|
||
# Ignore CLI configuration files | ||
.terraformrc | ||
terraform.rc |