Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CODEOWNERS #1212

Merged
merged 1 commit into from
Jun 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 24 additions & 3 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -1,7 +1,28 @@
# This file defines the persons who will be assigned as reviewers for PRs that
# modify particular files in the repo. The PR can be merged when approved by at
# least one codeowner. However, all Qiskit team members can (and should!) review the PRs.
# This file defines the set of people responsible for different sections of the
# Qiskit code.
#
# Being listed as a code owner on a section here means that user is empowered
# to approve and merge pull requests for that section of code. It also comes
# with an expected responsibility to review and maintain those subsections of
# the repository.
#
# A PR can be merged when approved by at least one codeowner. For PRs that touch
# more than one section with non-overlapping codeowners more than one codeowner
# may be required to approve a PR.
#
# However, every contributor to Qiskit can (and should!) review open PRs. This
# file is just about outlining responsibility for maintainership and final
# review/merging of PRs in different subsections of the repository.

# Global rule, unless specialized by a later one
* @stefan-woerner @woodsp-ibm @mrossinek

# Qiskit Nature modules
mappers/ @stefan-woerner @woodsp-ibm @mrossinek @ftroisi
operators/ @stefan-woerner @woodsp-ibm @mrossinek @ftroisi

# Override the release notes directories to have _no_ code owners, so any review
# from somebody with write access is acceptable.
/docs
/releasenotes/notes
/tools