Thank you for your interest in contributing to git2txt-cli! This document provides guidelines and instructions for contributing to the project.
By participating in this project, you agree to maintain a respectful and inclusive environment for all contributors.
- Fork the repository
- Create a new branch for your feature or fix
- Make your changes
- Submit a pull request
- Clone your fork:
git clone https://github.com/your-username/git2txt-cli.git
cd git2txt-cli
- Install dependencies:
npm install
- Create a branch:
git checkout -b feature/your-feature-name
- Use ES Modules (import/export)
- Follow existing code style
- Add comments for complex logic
- Maintain cross-platform compatibility
- Test your changes on different operating systems if possible
- Use clear and descriptive commit messages
- Start with a verb in present tense (e.g., "Add feature" not "Added feature")
- Reference issues when applicable
Example:
Add file size threshold configuration
- Implement --threshold flag
- Add validation for threshold value
- Update documentation
- Update the README.md with details of changes if needed
- Update the version number following SemVer
- Ensure all tests pass
- Link any related issues
- Provide a clear description of your changes
Before submitting a pull request:
- Test your changes locally
- Verify cross-platform compatibility
- Check for any performance impacts
- Ensure documentation is updated
When reporting issues, please include:
- A clear description of the problem
- Steps to reproduce
- Expected behavior
- Actual behavior
- System information (OS, Node.js version)
- Any relevant error messages or logs
git2txt-cli/
├── index.js # Main CLI entry point
├── package.json # Project configuration
├── README.md # Documentation
└── CONTRIBUTING.md # This file
By contributing to git2txt-cli, you agree that your contributions will be licensed under the MIT License.