docs: add contributing guidelines and github templates#20
Conversation
|
@kavix is attempting to deploy a commit to the ClaraClency Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 26 minutes and 36 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR adds standardized contribution templates and rewrites the contribution guide. Three new GitHub issue/PR templates define structured forms for bug reports, feature requests, and pull requests. The CONTRIBUTING.md guide is rewritten with explicit prerequisites, local development setup steps for backend and frontend, testing guidance, code style and commit conventions, and PR workflow. README.md is simplified to reference the new CONTRIBUTING.md. ChangesContribution Process Standardization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/ISSUE_TEMPLATE/bug_report.md:
- Around line 26-29: Replace the incorrect "iOS" example in the "Desktop (please
complete the following information):" section with appropriate desktop OS
examples; update the Browser/Version lines if desired to keep examples coherent
(suggested replacements: "macOS", "Windows 10", or "Ubuntu 22.04") so the
Desktop example reflects actual desktop operating systems.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e6038e2a-a8e3-4cb2-bd59-ba1c708e3c55
📒 Files selected for processing (5)
.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/feature_request.md.github/pull_request_template.mdCONTRIBUTING.mdREADME.md
✅ Deploy Preview for livedit canceled.
|
Add Contributing Guidelines and GitHub Templates
#13
Fixes #42
Summary
This PR introduces comprehensive contributor documentation and standardized GitHub templates to streamline onboarding, improve contribution quality, and establish consistent development workflows across the project.
Changes Made
1. Added
CONTRIBUTING.mdCreated a detailed contribution guide covering:
Development Environment Setup
Testing Guidelines
Code Style Standards
Git Workflow
feat,fix,docs, etc.)Pull Request Process
Issue Reporting
2. Added GitHub Templates
Introduced standardized templates to improve issue and PR quality:
.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/feature_request.md.github/pull_request_template.md3. Updated
README.mdCONTRIBUTING.mdguide in the Contributing section.Motivation
These additions lower the barrier to entry for new contributors, provide clear development standards, and help maintain code quality through a consistent contribution process. Standardized templates also reduce review friction by ensuring that issues and pull requests contain the necessary information from the start.
Checklist
CONTRIBUTING.mdwith setup, style, and contribution guidelinesREADME.mdto link to the contribution guideSummary by CodeRabbit