CODEOWNERS

# Defines the owners for the files in the repository branch.
# Automatically triggers an optional review by the associated code owner when a mapped file is changed in a pull request
# Later file mappings take precedence. Multiple code owners are allowed for each mapping.
# Reviews are mandatory when "Settings" / "Branches" / "Protect this branch" / "Require pull request reviews before merging" / "Require review from Code Owners" is enabled
# When mandatory, the code owner must have write access to the repository for the approval to allow the merge to proceed.
# So if code owner reviews are made mandtory, then "digital-playbook-reviewers" teams would need to be granted write access (currently read only).

# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @canada-ca/digital-playbook-admins will be requested for
# review when someone opens a pull request.
*       @canada-ca/digital-playbook-code

# Asset owners
/assets/  @canada-ca/digital-playbook-code

# JavaScript file owners
*.js    @canada-ca/digital-playbook-code

# CSS file owners
*.css    @canada-ca/digital-playbook-code

# HTML file owners
*.html  @canada-ca/digital-playbook-code

# JSON file owners
*.json  @canada-ca/digital-playbook-code

# YAML file owners
*.yml  @canada-ca/digital-playbook-code

# Data owners
/_data/  @canada-ca/digital-playbook-code

# Layouts owners
/_layouts/  @canada-ca/digital-playbook-code

# Includes owners
/_includes/  @canada-ca/digital-playbook-code

# Function owners
/_includes/functions/  @canada-ca/digital-playbook-code

# Views owners (covers /views/ and /_includes/views/)
views/ @canada-ca/digital-playbook-views

# Standard 1 owners
/en/1-design-with-users.md  @canada-ca/digital-playbook-standard-1
/fr/1-concevoir-avec-utilisateurs.md  @canada-ca/digital-playbook-standard-1

# Standard 2 owners
/en/2-build-in-accessibility-from-start.md  @canada-ca/digital-playbook-standard-2
/fr/2-integrer-accessibilite-des-depart.md  @canada-ca/digital-playbook-standard-2

# Standard 3 owners
/en/3-collaborate-widely.md  @canada-ca/digital-playbook-standard-3
/fr/3-collaborer-largement.md  @canada-ca/digital-playbook-standard-3

# Standard 4 owners
/en/4-empower-staff-deliver-better-services.md  @canada-ca/digital-playbook-standard-4
/fr/4-permettre-personnel-offrir-meilleurs-services.md  @canada-ca/digital-playbook-standard-4

# Standard 5 owners
/en/5-work-in-open-by-default.md  @canada-ca/digital-playbook-standard-5
/fr/5-travailler-ouvertement-par-defaut.md  @canada-ca/digital-playbook-standard-5

# Standard 6 owners
/en/6-use-open-standards-solutions.md  @canada-ca/digital-playbook-standard-6
/fr/6-utiliser-normes-solutions-ouvertes.md  @canada-ca/digital-playbook-standard-6

# Standard 7 owners
/en/7-iterate-improve-frequently.md  @canada-ca/digital-playbook-standard-7
/fr/7-effectuer-iterations-ameliorations-constamment.md  @canada-ca/digital-playbook-standard-7

# Standard 8 owners
/en/8-design-ethical-services.md  @canada-ca/digital-playbook-standard-8
/fr/8-concevoir-services-ethiques.md  @canada-ca/digital-playbook-standard-8

# Standard 9 owners
/en/9-address-security-privacy-risks.md  @canada-ca/digital-playbook-standard-9
/fr/9-gerer-risques-matiere-securite-protection-renseignements-personnels.md  @canada-ca/digital-playbook-standard-9

# Standard 10 owners
/en/10-be-good-data-stewards.md  @canada-ca/digital-playbook-standard-10
/fr/10-etre-bons-utilisateurs-donnees.md  @canada-ca/digital-playbook-standard-10