Repository navigation
BAI-1078 add CODEOWNERS - #197
Conversation
There was a problem hiding this comment.
LGTM, straightforward config addition.
What was reviewed: the new .github/CODEOWNERS file — confirmed it is valid CODEOWNERS syntax (comment lines plus one wildcard rule mapping * to three GitHub usernames). No code paths, build config, or security-sensitive logic are touched.
Extended reasoning...
The diff adds a single 3-line .github/CODEOWNERS file assigning a wildcard ownership rule to three usernames; it is a pure governance/config change with no effect on application code, build, or security-sensitive logic. The file uses valid CODEOWNERS syntax and there is no pre-existing CODEOWNERS file it conflicts with or overrides. This is mechanical and self-contained, so no human review is strictly required.
alvinhenrick
left a comment
There was a problem hiding this comment.
Hi Sean, I checked the diff: one CODEOWNERS change under BAI-1078, with a clean commit message. GitHub's CODEOWNERS validation reports no errors on the new line, no other CODEOWNERS file is shadowed, and the checks are green at this head. I can't tell from here whether the listed owners are the right people, so that part is yours to confirm.
Adds a CODEOWNERS file to icanbwell/SparkAutoMapper 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.
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.