Skip to content

Commit e31b824

Browse files
authored
Remove duplicate example sections
1 parent 5df1f7e commit e31b824

File tree

1 file changed

+4
-15
lines changed
  • content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository

1 file changed

+4
-15
lines changed

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md

Lines changed: 4 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,10 @@ apps/ @octocat
9999
# subdirectories.
100100
/docs/ @doctocat
101101
102+
# In this example, any change inside the `/scripts` directory
103+
# will require approval from @doctocat or @octocat.
104+
/scripts/ @doctocat @octocat
105+
102106
# In this example, @octocat owns any file in the `/apps`
103107
# directory in the root of your repository except for the `/apps/github`
104108
# subdirectory, as its owners are left empty.
@@ -114,21 +118,6 @@ There are some syntax rules for gitignore files that do not work in CODEOWNERS f
114118
## CODEOWNERS and branch protection
115119
Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
116120

117-
### Example of a CODEOWNERS file
118-
```
119-
# In this example, any change inside the `/apps` directory
120-
# will require approval from @doctocat.
121-
/apps/ @doctocat
122-
123-
# In this example, any change inside the `/apps` directory
124-
# will require approval from @doctocat or @octocat.
125-
/apps/ @doctocat @octocat
126-
127-
# In this example, any change inside the `/apps` directory
128-
# will require approval from a member of the @example-org/content team.
129-
/apps/ @example-org/content-team
130-
```
131-
132121

133122
## Further reading
134123

0 commit comments

Comments
 (0)