Skip to content
GitLab
Explore
Sign in
parity
sub-flood
Compare revisions
0a31c71fd2e9c47198c08c6765bdc3bf8767bb37 to 7cac950144e10daf8f1f2daf3c16fdc23cb95710
Commits on Source (2)
Add CODEOWNERS file
· 5ac9467d
Sergej Kostjucenko
authored
Nov 23, 2021
5ac9467d
Merge pull request #48 from paritytech/sk-add-codeowners-file
· 7cac9501
Sergejs Kostjucenko
authored
Nov 23, 2021
Add `CODEOWNERS` file
7cac9501
Hide whitespace changes
Inline
Side-by-side
CODEOWNERS
0 → 100644
View file @
7cac9501
# Lists some code owners.
#
# A codeowner just oversees some part of the codebase. If an owned file is changed then the
# corresponding codeowner receives a review request. An approval of the codeowner might be
# required for merging a PR (depends on repository settings).
#
# For details about syntax, see:
# https://help.github.com/en/articles/about-code-owners
# But here are some important notes:
#
# - Glob syntax is git-like, e.g. `/core` means the core directory in the root, unlike `core`
# which can be everywhere.
# - Multiple owners are supported.
# - Either handle (e.g, @github_user or @github_org/team) or email can be used. Keep in mind,
# that handles might work better because they are more recognizable on GitHub,
# eyou can use them for mentioning unlike an email.
# - The latest matching rule, if multiple, takes precedence.
# CI
/.github/
@paritytech/ci
@radupopa2010
/.maintain/
@paritytech/ci
@radupopa2010
/scripts/
@paritytech/ci
@radupopa2010
/.gitlab-ci.yml
@paritytech/ci
@radupopa2010