As a collaborator I need to know who I can request to review my pull request so my work doesn't get lost in the noise
Adding a CODEOWNERS file to our repositories can do two things for us. One it'll give a clear place where our contributors can see who is responsible for what. Second it automatically assigns the correct person when that section of the repository is touched, so they are made aware and can review.
james-dow created the following on Apr 26:
As a collaborator I need to know who I can request to review my pull request so my work doesn't get lost in the noise
Adding a CODEOWNERS file to our repositories can do two things for us. One it'll give a clear place where our contributors can see who is responsible for what. Second it automatically assigns the correct person when that section of the repository is touched, so they are made aware and can review.
Resources for reference
Acceptance criteria
CODEOWNERS.md
file exists for v18 within.github
folder.CODEOWNERS.md
file exists for v18-starter-kit within.github
folder.CODEOWNERS.md
file exists for v19a within.github
folder.CODEOWNERS.md
file exists for patterns within.github
folder.CODEOWNERS.md
file exists for digital-design within.github
folder.CODEOWNERS.md
file exists for carbon-integration-poc within.github
folder.CODEOWNERS.md
file exists for northstar-external-website within.github
folder.CODEOWNERS.md
file exists for IBM/carbon-addons-dotcom within.github
folder.CODEOWNERS.md
file exists for IBM/dotcom-services within.github
folder.CODEOWNERS.md
file exists for IBM/dotcom-bundles within.github
folder.CODEOWNERS.md
file exists for IBM/dotcom-website within.github
folder.Original issue: https://github.ibm.com/webstandards/digital-design/issues/755