|
| 1 | +# Contributing to `image-optimize-cli` |
| 2 | + |
| 3 | +Thank you for your interest in contributing to `image-optimize-cli`! We welcome contributions of all types, from bug fixes and features to documentation improvements. Please follow these guidelines to help us maintain a high-quality project. |
| 4 | + |
| 5 | +## Getting Started |
| 6 | + |
| 7 | +1. **Fork the Repository**: Click the "Fork" button at the top right of the repository page to create your own copy of the project. |
| 8 | + |
| 9 | +2. **Clone Your Fork**: Clone your forked repository to your local machine using: |
| 10 | + ```sh |
| 11 | + git clone https://github.com/your-username/image-optimize-cli.git |
| 12 | + ``` |
| 13 | + |
| 14 | +3. **Create a New Branch**: Create a new branch for your work. It's good practice to name your branch descriptively based on the changes you're making. |
| 15 | + ```sh |
| 16 | + git checkout -b my-feature-branch |
| 17 | + ``` |
| 18 | + |
| 19 | +4. **Make Changes**: Implement your changes in the code. If you're adding a new feature or fixing a bug, make sure to write clear and concise commit messages. |
| 20 | + |
| 21 | +5. **Run Tests**: Ensure that all tests pass before submitting your changes. If you’re adding new features, consider writing tests for them as well. |
| 22 | + ```sh |
| 23 | + npm test |
| 24 | + ``` |
| 25 | + |
| 26 | +6. **Commit Your Changes**: Commit your changes with a descriptive message. |
| 27 | + ```sh |
| 28 | + git add . |
| 29 | + git commit -m "Describe your changes here" |
| 30 | + ``` |
| 31 | + |
| 32 | +7. **Push Your Branch**: Push your changes to your forked repository. |
| 33 | + ```sh |
| 34 | + git push origin my-feature-branch |
| 35 | + ``` |
| 36 | + |
| 37 | +8. **Open a Pull Request**: Go to the original repository and open a pull request from your forked repository and branch. Provide a clear description of your changes and why they are needed. |
| 38 | + |
| 39 | +## Coding Guidelines |
| 40 | + |
| 41 | +- **Follow the Code Style**: Ensure your code adheres to the existing code style of the project. This includes formatting, naming conventions, and coding practices. |
| 42 | + |
| 43 | +- **Write Tests**: If you're adding new features or fixing bugs, include tests to cover your changes. Ensure that all existing tests pass. |
| 44 | + |
| 45 | +- **Documentation**: Update the documentation if your changes affect how the project is used or configured. This includes README, code comments, and inline documentation. |
| 46 | + |
| 47 | +## Reporting Issues |
| 48 | + |
| 49 | +If you find a bug or have a feature request, please open an issue on the [issue tracker](https://github.com/muhammad-fiaz/image-optimize-cli/issues). Provide as much detail as possible, including steps to reproduce the issue, expected behavior, and actual behavior. |
| 50 | + |
| 51 | +## Contact |
| 52 | + |
| 53 | +For any questions or additional help, feel free to reach out to the maintainers via the [issue tracker](https://github.com/muhammad-fiaz/image-optimize-cli/issues) or join [discord](https://discord.com/invite/pMw7nfBzXz) directly. |
| 54 | + |
| 55 | +--- |
| 56 | + |
| 57 | +Thank you for contributing to `image-optimize-cli`! |
| 58 | + |
0 commit comments