Files
pezkuwi-subxt/CODEOWNERS
T
Line: 20: incorrect codeowner organization: paritytech/ci Line: 20: incorrect codeowner user: chevdor Line: 20: no users/groups matched Line: 21: incorrect codeowner organization: paritytech/ci Line: 21: no users/groups matched Line: 22: incorrect codeowner organization: paritytech/ci Line: 22: no users/groups matched Line: 23: incorrect codeowner organization: paritytech/ci Line: 23: incorrect codeowner user: chevdor Line: 23: no users/groups matched Line: 24: incorrect codeowner organization: paritytech/ci Line: 24: incorrect codeowner user: chevdor Line: 24: no users/groups matched Line: 27: incorrect codeowner user: chevdor Line: 27: no users/groups matched
2021-11-22 17:13:49 +02:00

28 lines
1.1 KiB
Plaintext

# 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/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 @chevdor
/.gitlab-ci.yml @paritytech/ci
/scripts/ci/ @paritytech/ci
/scripts/github/ @paritytech/ci @chevdor
/scripts/extrinsic-ordering-filter.sh @paritytech/ci @chevdor
# CHANGELOG
/scripts/changelog/ @chevdor