Contribution
Thank you for your interest in contributing to SwiftPay! While this is primarily a solo project, we happily welcome contributions from the community. This document provides guidelines and steps for contributing.
🎯 Types of Contributions We're Looking For
- Bug fixes
- Documentation improvements
- Code optimization
- New features aligned with the project roadmap
- Test cases
- Typo corrections
- Translation help
🚀 Getting Started
-
Fork the Repository
# Clone your fork
git clone https://github.com/nb3n/swiftpay-docs
cd swiftpay-docs
# Add upstream remote
git remote add upstream https://github.com/original/swiftpay-docs.git -
Create a Branch
# Create a new branch for your feature
git checkout -b feature/your-feature-name
# or
git checkout -b fix/your-bug-fix
📝 Development Process
-
Setup Development Environment
# Install dependencies
npm install # or yarn install
# Run tests
npm test # or yarn test
# Start development server
npm run dev # or yarn dev -
Make Your Changes
- Write clean, maintainable code
- Follow existing code style
- Add comments where necessary
- Update documentation if needed
-
Test Your Changes
- Add/update tests for new features
- Ensure all tests pass
- Test across different environments if applicable
📤 Submitting Changes
-
Commit Your Changes
git add .
git commit -m "Brief description of your changes" -
Pull Request Guidelines
- Use a clear, descriptive title
- Include relevant issue numbers if applicable
- Provide detailed description of changes
- Add screenshots for UI changes
💻 Commit Message Format
type(scope): Brief description
Detailed description if needed
Fixes #issue_number
Types:
feat
: New featurefix
: Bug fixdocs
: Documentation changesstyle
: Code style changesrefactor
: Code refactoringtest
: Adding/updating testschore
: Maintenance tasks
🔍 Code Review Process
- Maintainer will review your PR within 3-5 business days
- Changes may be requested
- Once approved, PR will be merged