Thank you for considering contributing to this project! This document outlines the guidelines for contributing to the eslint-plugin-code-complete project.
Please be respectful and considerate when interacting with other contributors.
If you find a bug, please create an issue on GitHub with the following information:
- Clear description of the bug
- Steps to reproduce the issue
- Expected behavior
- Actual behavior
- Environment information (ESLint version, Node.js version, etc.)
If you want to suggest an enhancement or a new rule, please create an issue with:
- A clear description of the problem or use case
- Your proposed solution
- Examples of code that would pass/fail
- Fork the repository
- Create a new branch for your changes
- Add or modify code
- Add or update tests
- Ensure all tests pass with
pnpm test - Update documentation if necessary
- Submit a pull request
# Clone the repository
git clone https://github.com/your-username/eslint-plugin-code-complete.git
cd eslint-plugin-code-complete
# Install dependencies
pnpm install
# Run tests
pnpm test- Create a new file in the
rulesdirectory - Add the rule to
rules/index.ts - Add the rule to
index.ts - Create tests in the
testsdirectory - Add documentation to the README
- Write clean, readable, and maintainable code
- Follow the existing code style
- Include appropriate comments
- Write tests for all features
- Keep functions small and focused
All changes should be thoroughly tested. Run the test suite with:
pnpm testUpdate the README.md file to reflect any changes to the API or behavior of the rules.
By contributing to eslint-plugin-code-complete, you agree that your contributions will be licensed under the project's MIT License.