Files
pezkuwi-subxt/CODEOWNERS
T
Line: 20: incorrect codeowner organization: paritytech/ci Line: 20: incorrect codeowner organization: paritytech/release-engineering 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: incorrect codeowner organization: paritytech/release-engineering Line: 22: no users/groups matched
Alexander Samusev 4eeb3c851f [ci] use external repo for check-labels (#1985)
* [ci] use external repo for check-labels

* remove ruled_labels specs, docs

* remove repo checkout

* remove checkout action

* remove old gha
2022-12-13 10:57:52 +01:00

24 lines
1002 B
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 @paritytech/release-engineering
/.gitlab-ci.yml @paritytech/ci
/scripts/ci/ @paritytech/ci @paritytech/release-engineering