Thank you for your interest in contributing to Prehacks! This document provides guidelines and information for contributors.
- Fork the repository
- Clone your fork locally
- Create a new branch for your feature or bugfix
- Make your changes
- Add tests for your changes
- Ensure all tests pass
- Submit a pull request
# Clone the repository
git clone https://github.com/yourusername/prehacks.git
cd prehacks
# Install dependencies
npm install # or appropriate package manager
# Run tests
npm test
# Run linting
npm run lint- Follow the existing code style and conventions
- Use meaningful variable and function names
- Add comments for complex logic
- Ensure your code is properly formatted
- Write tests for new features
- Ensure existing tests continue to pass
- Aim for good test coverage
- Update the CHANGELOG.md with your changes
- Ensure your PR description clearly explains what was changed and why
- Link any related issues
- Request review from maintainers
When reporting issues, please include:
- Clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Environment details (OS, version, etc.)
Feel free to open an issue for questions or discussions.