# Define individuals or teams who are responsible for code in a # repository (i.e. who gets requested for a review by default). # Order is important; the last matching pattern takes the most # precedence. # Tip: IDEs like PyCharm may have features or extensions that validate # CODEOWNERS files and check that paths that are listed match any files. * @PlasmaPy/plasmapy-reviewers # subpackages *pytest_helpers/ @namurphy analysis/ @rocco8773 diagnostics/ @rocco8773 **/diagnostics/charged_particle_radiography/ @pheuer dispersion/ @ejohnson-96 **/utils/decorators/ @rocco8773 # subpackage files (with wildcards to include tests) **/analysis/*nullpoint.py @namurphy **/diagnostics/*thomson.py @pheuer **/formulary/*relativity.py @namurphy # documentation .readthedocs.yml @namurphy docs/_author_list_from_cff.py @namurphy docs/_global_substitutions.py @namurphy docs/conf.py @namurphy docs/contributing/ @namurphy docs/plasmapy_sphinx/ @rocco8773 # project files ci_requirements/ @namurphy mypy.ini @namurphy pyproject.toml @namurphy type_stubs/ @namurphy # tests, linters, CI .github/ @namurphy .pre-commit-config.yaml @namurphy codecov.yml @namurphy noxfile.py @namurphy