CODEOWNERS

# This is a comment.
# 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

# 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

# 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

# Start of NVDA config

# By default auto request review from NV Access developer team.
* @nvaccess/developers

# For changes to the userGuide auto request review from userDocs team
/user_docs/en/userGuide.t2t @nvaccess/userDocs

# For various project documentation, require appropriate teams
/projectDocs/community/ @nvaccess/userDocs
/projectDocs/testing/ @nvaccess/userDocs @nvaccess/developers
/projectDocs/issues/ @nvaccess/userDocs @nvaccess/developers
/readme.md @nvaccess/userDocs @nvaccess/developers
security.md @nvaccess/userDocs @nvaccess/developers
CODE_OF_CONDUCT.md @nvaccess/userDocs @nvaccess/developers
.github/CONTRIBUTING.md @nvaccess/userDocs @nvaccess/developers