docs: add PR review guidelines for community reviewers#2271
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAdds ChangesPR Review Guidelines Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📋 Issue PlannerBuilt with CodeRabbit's Coding Plans for faster development and fewer bugs. View plan used: ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8c5927e4-585e-4523-a1f5-6054cdcad600
📒 Files selected for processing (1)
docs/sdk_developers/pr_review_guidelines.md
Closes hiero-ledger#2228 Create a comprehensive guide at docs/sdk_developers/pr_review_guidelines.md for community members reviewing pull requests labeled 'reviewer: community'. The document covers: - Quality checks (GPG/DCO signing, issue linkage, CI workflow checks) - Review best practices (communication style, research process, AI caution) - DO/DON'T quick reference checklist - Cross-references to related documentation and help resources Signed-off-by: Anshul Kushwaha <137977998+sudo-anshul@users.noreply.github.com>
e4866dd to
93ad03d
Compare
exploreriii
left a comment
There was a problem hiding this comment.
Great guide! Thank you
manishdait
left a comment
There was a problem hiding this comment.
@sudo-anshul, Please update the branch
AntonioCeppellini
left a comment
There was a problem hiding this comment.
thanks for your contribution @sudo-anshul :D great work!
|
👋 Hi @sudo-anshul! Great work completing a Good First Issue issue! 🎉 Thanks for your contribution! 🚀 Here are some issues you might want to explore next:
🌟 Stay connected: Happy coding! 🚀 |
|
thank you all so much for the support and quick reviews! a huge thanks to @exploreriii for assigning the issue, guiding through the process, and merging the PR.. really appreciated! thanks to @manishdait for the review and feedback, and @AntonioCappiello for the encouragement... it means a lot! this was a great first experience contributing to the Hiero Python SDK. looking forward to more!! |
…2271) Signed-off-by: Anshul Kushwaha <137977998+sudo-anshul@users.noreply.github.com>
Description:
Add PR review guidelines document for community reviewers.
docs/sdk_developers/pr_review_guidelines.mdcovering quality checks, review best practices, and a DO/DON'T checklistRelated issue(s):
Fixes #2228
Notes for reviewer:
docs/sdk_developers/(H1 title, TOC, numbered H2 sections, DO ✅ / DON'T ❌ format, "Need Help?" footer)Checklist