chore: add prayagupa as a code owner - #3626
Conversation
Prayag joins the maintainer-approval gate alongside Liam so both can review and merge, including each other's PRs. Requires the matching repository permission grant (Maintain), done separately in settings. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
PR Review Summary
Verdict: AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims. |
There was a problem hiding this comment.
Pull request overview
Updates repository-wide CODEOWNERS to include an additional maintainer so that their approvals satisfy the require_code_owner_review branch protection gate.
Changes:
- Adds
@prayagupato the global (*) CODEOWNERS entry alongside the existing owners.
Show a summary per file
| File | Description |
|---|---|
.github/CODEOWNERS |
Adds @prayagupa to the * ownership line so they can provide required code-owner approvals. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
|
liamcrumm this one needs you specifically, and it is worth jumping the queue for. The bind: this PR widens the code-owner set from two to three, and It is one line, green, and has been open seven days. Prayag (@prayagupa) is already reviewing: three reviews on the currently-open queue. The grant just means that effort can end in a merge instead of a comment. I went through the open backlog today and the shape is consistent with this being the constraint rather than a nice-to-have. Attention, not throughput: median time from open to merge is one day and p90 is eight, so when either of you touches a PR it lands quickly. What accumulates is everything untouched. Twenty-seven open PRs have never had a human review, the oldest twelve days, and twenty-two more had a review, got a response from the author, and then went quiet. I have reviewed eleven of the never-reviewed ones today, including #3659, #3660, #3555, #3569, #3676 and #3674, several of which close fail-open paths against issues MohammadHaroonAbuomar filed himself. None of that helps until someone with the bit merges them, which is the same problem this PR fixes. I am not a code owner, so this comment is all the leverage I have on it. |
Adds Prayag (@prayagupa) to the
*code-owner line so their approvals satisfy the require_code_owner_review gate, alongside MohammadHaroonAbuomar and liamcrumm — per maintainer decision so Prayag and Liam can both review and merge, including each other's PRs.Pairs with the repository permission grant (Maintain) done in settings; the CODEOWNERS entry has no effect until that grant exists.