CODEOWNERS

# Please once you will have some ownership of some package/module, you can add
# it here to be requested for review of comming PRs which are changing the code
# you own.

# Each line is a file pattern followed by one or more owners.

# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @global-owner1 and @global-owner2 will be requested for
# review when someone opens a pull request.
#*       @global-owner1 @global-owner2
# We have nested team under OCS-QE team for top level reviewers, so everyone
# who is part of this team will be requested for revew for upcomming PRs for
# all changes.
*   @red-hat-storage/top-level-reviewers

# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
#*.js    @js-owner

# You can also use email addresses if you prefer. They'll be
# used to look up users just like we do for commit author
# emails.
#*.go docs@example.com

# 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

# Turquoise-squad
/tests/functional/disaster-recovery/ @red-hat-storage/turquoise-squad

# Aqua-squad
/tests/lvmo/ @red-hat-storage/aqua-squad

# Brown-squad
/tests/cross_functional/resilience/ @red-hat-storage/brown-squad
/tests/functional/nfs_feature/ @red-hat-storage/brown-squad
/tests/functional/odf-cli/ @red-hat-storage/brown-squad
/tests/functional/pod_and_daemons/ @red-hat-storage/brown-squad
/tests/functional/z_cluster/ @red-hat-storage/brown-squad

# Green-squad
/tests/functional/pv/pv_services/ @red-hat-storage/green-squad
/tests/functional/storageclass/ @red-hat-storage/green-squad
/tests/functional/encryption/ @red-hat-storage/green-squad

# Blue-squad
/tests/functional/monitoring/ @red-hat-storage/blue-squad

# Red-squad
/tests/functional/object/mcg/  @red-hat-storage/red-squad
/tests/functional/object/rgw/  @red-hat-storage/red-squad

# Purple-squad
/tests/functional/upgrade/ @red-hat-storage/purple-squad

# Magenta-squad
/tests/functional/workloads/ @red-hat-storage/magenta-squad
/tests/cross_functional/flowtest/ @red-hat-storage/magenta-squad
/tests/cross_functional/kcs/ @red-hat-storage/magenta-squad
/tests/cross_functional/longevity/ @red-hat-storage/magenta-squad
/tests/cross_functional/system_test/ @red-hat-storage/magenta-squad

# Grey-squad
/tests/cross_functional/performance/ @red-hat-storage/grey-squad

# Orange-squad
/tests/cross_functional/scale/ @red-hat-storage/orange-squad

# Black-squad
/tests/functional/ui/ @red-hat-storage/black-squad
/tests/cross_functional/ui/ @red-hat-storage/black-squad
/ocs_ci/ocs/ui/ @red-hat-storage/black-squad

# 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.
#/docs/ @doctocat