Contributing
Guidelines for contributing to ShipKit, including code standards, pull request process, testing requirements, and documentation
Contributing to ShipKit
Thank you for your interest in contributing to ShipKit! This guide will help you understand our development process and how to contribute effectively.
Code of Conduct
We are committed to providing a welcoming and inclusive experience for everyone. Please read our Code of Conduct before contributing.
Getting Started
-
Fork the Repository
-
Install Dependencies
-
Set Up Development Environment
Development Process
Branch Naming
- Feature:
feature/description
- Bug Fix:
fix/description
- Documentation:
docs/description
- Performance:
perf/description
- Refactor:
refactor/description
Commit Messages
We use Conventional Commits for clear communication:
Code Style
Testing Requirements
-
Unit Tests
-
Integration Tests
-
E2E Tests
Pull Request Process
-
Create Feature Branch
-
Make Changes
-
Open Pull Request
- Use the PR template
- Link related issues
- Add meaningful description
- Include screenshots/videos if UI changes
- Request reviews from maintainers
-
Address Reviews
Documentation
Code Comments
API Documentation
Component Documentation
Review Process
Code Review Checklist
-
Functionality
- [ ] Code works as expected
- [ ] Edge cases handled
- [ ] Error states managed
- [ ] Performance considered
-
Code Quality
- [ ] TypeScript types used correctly
- [ ] Code is readable and maintainable
- [ ] No unnecessary complexity
- [ ] Follows project conventions
-
Testing
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] E2E tests added/updated
- [ ] Test coverage maintained
-
Documentation
- [ ] Code comments added
- [ ] API documentation updated
- [ ] Component documentation updated
- [ ] README updated if needed
Review Comments
Release Process
-
Version Bump
-
Create Release
-
Deploy Release
Getting Help
Additional Resources