Thank you for your interest in contributing to TransTrack! This document provides guidelines for contributing to the project.
Please be respectful and professional in all interactions. We are committed to providing a welcoming environment for everyone.
- Node.js 18 or higher
- npm 9 or higher
- Git
-
Fork the repository
-
Clone your fork:
git clone https://github.com/YOUR_USERNAME/TransTrack.git cd TransTrack -
Install dependencies:
npm install
-
Start development:
npm run dev:electron
- Use ESLint for JavaScript/TypeScript linting
- Follow the existing code style
- Use meaningful variable and function names
- Add comments for complex logic
Use clear, descriptive commit messages:
feat: Add patient export to PDFfix: Correct priority calculation for kidney patientsdocs: Update installation instructionsrefactor: Simplify donor matching algorithm
-
Create a feature branch:
git checkout -b feature/your-feature-name
-
Make your changes
-
Run tests and linting:
npm run lint npm test -
Push to your fork:
git push origin feature/your-feature-name
-
Create a Pull Request with:
- Clear description of changes
- Screenshots if UI changes
- Any breaking changes noted
When contributing, please ensure:
- No PHI in Code: Never include real patient data
- Audit Logging: All data modifications must be logged
- Access Control: Respect role-based permissions
- Security: Follow secure coding practices
- Write tests for new features
- Ensure existing tests pass
- Test on Windows, macOS, and Linux if possible
- Update documentation for new features
- Include JSDoc comments for functions
- Update the changelog
Open an issue for questions or discussions.
Thank you for contributing to TransTrack!