π₯ Multiple Ways to Help
Ways to Contribute
From code warriors to documentation heroes - there's a place for everyone in our community
π Simple 4-Step Process
How to Contribute
From finding issues to merging PRs - here's your roadmap to becoming a GitAura contributor
01
Find Issues or Bugs
Time to play detective with our codebase
Explore GitAura and spot bugs that need fixing or features that could be better
- Test different features thoroughly
- Check existing GitHub issues
- Look for UI/UX improvements
- Think about new useful features
02
Raise an Issue
Document your findings like a pro
Create detailed GitHub issues that make our team say 'wow, this person gets it'
- Use clear, descriptive titles
- Provide reproduction steps
- Include screenshots if relevant
- Suggest implementation ideas
03
Fork & Work
Time to get your hands dirty with code
Fork our repo, create your branch, and start building the solution
- Fork the GitAura repository
- Create feature branch
- Follow our coding standards
- Write tests for changes
04
Submit PR
The moment of truth - get your code reviewed
Submit a clean PR and watch our team marvel at your coding skills
- Create detailed pull request
- Link to original issue
- Ensure all tests pass
- Respond to review feedback
Tech Stack We Use
Next.js 14 with App Router
TypeScript
Tailwind CSS
Prisma & PostgreSQL
Clerk Authentication
GitHub API
Contribution Guidelines
Follow TypeScript best practices
Write meaningful commit messages
Add tests for new features
Keep PRs focused and small
Update documentation when needed
Be respectful in all interactions
π₯ Community Heroes
Meet Our Contributors
These amazing developers are building the future of GitHub analytics with us
Loading our amazing contributors...