We're happy you're interested in contributing! This document provides guidelines and instructions for contributing.
- Be respectful
- Provide constructive feedback
- Focus on the best outcome for the project
- Fork the repository
- Create a new branch for your feature/fix
- Setup your development environment (see Development Guide)
As this project handles financial transactions:
- Always consider security implications
- Never commit sensitive data (keys, credentials)
- Follow secure coding practices
- When in doubt, ask for a security review
- Run
npm run lint
before committing - Run
npm run format
to format code - Follow TypeScript best practices
- Write clear, self-documenting code
- Add comments for complex logic
- Add tests for new features
- Run
npm run test
to ensure all tests pass - Aim for good test coverage
- Include both happy and error paths
- Update documentation for any changes
- Ensure all tests pass
- Update the changelog if applicable
- Create a clear PR description explaining:
- What changes you made
- Why you made them
- How to test them
- Any breaking changes
- At least one maintainer must review and approve
- All automated checks must pass
- Security-critical changes require additional review
- Open an issue for questions
- Tag maintainers for urgent matters
- Join our community discussions
See our Development Guide for detailed setup instructions.