chore: expand code ownership for SDK, wallet stack, proof verifier and wasm-dpp2#3840
Conversation
…crates Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CODEOWNERS file is modified to add ChangesOwnership Assignments
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
…asm-dpp2 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Issue being fixed or feature implemented
Code-owner review is required on
v3.1-dev, but ownership didn't reflect who actually works on each area, so PRs bottleneck on a single owner.What was done?
Updated CODEOWNERS:
packages/swift-sdk/: added@llbarteklland@ZocoLinirs-platform-wallet,-ffi,-storage): owned by@QuantumExplorer@shumkov@lklimek@llbartekll@ZocoLinipackages/rs-sdk/andpackages/rs-sdk-ffi/: added@lklimekpackages/rs-drive-proof-verifier/: new entry —@QuantumExplorer@shumkov@lklimekpackages/wasm-dpp2/: new entry —@QuantumExplorer@shumkovBecause CODEOWNERS is last-match-wins, anything outside these paths still falls back to
* @QuantumExplorer.How Has This Been Tested?
N/A — CODEOWNERS-only change. Verified all added handles have write access (required for entries to take effect) and that branch protection on
v3.1-devenforcesrequire_code_owner_reviews.Breaking Changes
None
Checklist:
For repository code-owners and collaborators only
🤖 Generated with Claude Code
Summary by CodeRabbit