SyntheticBird/cuprate-hinto-janai
1
0
Fork 0
mirror of https://github.com/hinto-janai/cuprate.git synced 2024-12-22 19:49:33 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

add codeowners

Browse source
This commit is contained in:
hinto.janai 2024-10-31 19:32:34 -04:00
parent ee72de1673
commit 78e20a4992
No known key found for this signature in database
GPG key ID: D47CE05FA175A499
1 changed files with 14 additions and 65 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

79
CODEOWNERS
View file

@ -1,67 +1,16 @@
# This is a comment. # For `CODEOWNERS` documentation, see:
# Each line is a file pattern followed by one or more owners. # <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners>
# These owners will be the default owners for everything in # Default owner(s) of all code.
# the repo. Unless a later match takes precedence, * @Boog900 @hinto-janai
# @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 # hinto-janai
# precedence. When someone opens a pull request that only /benches/** @hinto-janai
# modifies JS files, only @js-owner and not the global /books/architecture/** @hinto-janai
# owner(s) will be requested for a review. /books/user/** @hinto-janai
*.js @js-owner #This is an inline comment. /constants/** @hinto-janai
/rpc/** @hinto-janai
# You can also use email addresses if you prefer. They'll be /storage/blockchain/** @hinto-janai
# used to look up users just like we do for commit author /storage/database/** @hinto-janai
# emails. /test-utils/data/** @hinto-janai
*.go docs@example.com /test-utils/rpc/** @hinto-janai
# 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/* docs@example.com
# 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. Without an owner, changes
# to `apps/github` can be made with the approval of any user who has
# write access to the repository.
/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