Repository navigation
BAI-1078 add CODEOWNERS - #59
Conversation
There was a problem hiding this comment.
I reviewed this PR and didn't find any bugs. The file is syntactically valid, but the PR description itself says all three owners are a best guess, so someone on the team should confirm the list before it merges.
What was reviewed:
.github/CODEOWNERSis in a location GitHub recognizes, and it has a single valid catch-all*rule with no later rules that would override it.- Not done: I couldn't check from this checkout whether the three handles are real accounts with write access to the repo. GitHub ignores owners that don't have write access.
- No CODEOWNERS file existed before this one, so no reviewers will be requested automatically on this PR.
Extended reasoning...
This change adds one new file, .github/CODEOWNERS, with two comment lines and one catch-all rule naming three default owners for the whole repo. It changes no code and touches no security-sensitive code, but it does set who is accountable for review across the repository. I deferred because the PR description says each owner was added only to reach three people. Whether those handles exist and have write access can't be checked from the repository contents. Since the base branch has no CODEOWNERS file, the proposed owners won't be asked to review automatically, so a person needs to confirm the list.
Adds a CODEOWNERS file to icanbwell/mockserver_client so each change has a named group accountable for it.
Owners are the people with the most recent activity here, with team members added so there are at least three.
Some owners were added to reach three and are a best guess; if the list is wrong, edit the file in this PR or after it merges.
Evidence (last 90 days, share of commits, merged PRs and reviews):
Merge behavior: CODEOWNERS only requests reviewers on PRs here; it does not by itself block merging.
Edit the file in this PR directly if the owners should differ.
If this PR is approved, please merge it; there is no need to wait for Sean Hegarty.