Thank you for considering contributing to our project! This document outlines the process and guidelines for contributing.
In this repo, you can contribute these following:
- DevIniter Official Website
- Documents
If you want to contribute to DevIniter CLI's behaviors, please check this repo
By participating in this project, you agree to abide by our Code of Conduct. Please read it before contributing.
-
Fork the Repository
- Create your own fork of the project
- Clone it to your local machine
-
Create a Branch
git checkout -b feature/your-feature-name
-
Make Your Changes
- Write clean, documented code
- Follow the existing code style and conventions
- Add tests if applicable
-
Commit Your Changes
- Use clear and meaningful commit messages
- Follow conventional commits format:
feat: add new feature fix: resolve specific issue docs: update documentation
-
Push to Your Fork
git push origin feature/your-feature-name
-
Submit a Pull Request
- Fill in the pull request template
- Link any relevant issues
- Provide a clear description of your changes
-
Install dependencies:
npm install # or yarn install or pnpm install
-
Run tests:
npm test # or yarn test or pnpm test
- PRs should target the
master
branch - Include tests for new features
- Update documentation as needed
- Ensure all tests pass
- Follow the code style guidelines
- Use the issue tracker
- Include detailed steps to reproduce
- Specify your environment details
- Use the issue template if available
- Follow the established project coding style
- Use consistent indentation
- Add comments for complex logic
- Keep functions focused and concise
Feel free to reach out to the maintainers if you have any questions.
By contributing, you agree that your contributions will be licensed under the project's license.