Repository navigation
chore: sync OWNERS from maintainers.yaml - #115
mergeraptor[bot] wants to merge 0 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull request changes no files, so there is nothing to approve. |
There was a problem hiding this comment.
Routing to a human — OWNERS is a trust surface.
This is the same generated change as projectbluefin/common#1454 (adds bketelsen, removes tulilirockz in approvers, OWNERS:6/OWNERS:10); I posted the full verification there. The source maintainers.yaml in projectbluefin/.project is outside what I can read, so I cannot confirm the rotation was intentional. cc @castrojo — one answer there covers all six sibling PRs. I have not approved, labelled, or closed anything.
Confidence: 3/5 (needs attention) — 1 medium finding; 2 perspectives requires a human decision
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
a8beb19
|
|
/approve This regenerates OWNERS from |
a8beb19 to
a506754
Compare
Generated by projectbluefin/.project sync-owners.yml from
maintainers.yaml. Prow uses OWNERS for /approve and reviewer requests.