chore: route reviews to maintainer team - #1441
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughRepository governance metadata is updated by changing the default code owner and adding Clay Good to the Core Maintainers table. ChangesRepository governance
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
alfred-openspec
left a comment
There was a problem hiding this comment.
Reviewed the CODEOWNERS and maintainer-list updates, including the automation-maintainer entry. All required checks are green.
What changed
@Fission-AI/openspec-maintainersWhy
Review requests currently route only to Tabish. The new visible maintainer team has Maintain access to OpenSpec and is configured to auto-assign one reviewer using load balancing.
Impact
Once merged, new ready-for-review pull requests will route to an available maintainer instead of always requesting Tabish. The existing one-approval policy remains unchanged.
Validation
git diff --checkSummary by CodeRabbit