Thank you for considering contributing to My Image Fetcher Library! By contributing, you help improve the library and make it more valuable for others. Please take a moment to review this document to understand how you can contribute effectively.
There are several ways you can contribute to this project:
If you encounter any issues or bugs while using the library, please open a new issue on GitHub. Be sure to provide as much detail as possible, including the steps to reproduce the issue and your environment.
If you have ideas for enhancements or new features, please create an issue on GitHub to discuss your proposal. We welcome your input and feedback.
If you would like to contribute code to the project, follow these steps:
Make sure you have the necessary tools and dependencies installed. Refer to the README.md for instructions on setting up your development environment.
Follow the build instructions in the README.md to build the project locally.
Adhere to the coding guidelines specified in the Coding Guidelines section below.
Ensure that your changes do not break existing functionality. Write tests if necessary to cover your changes.
Write clear and concise commit messages. Follow the Commit Messages guidelines below.
-
Push your changes to your fork.
-
Create a pull request (PR) from your fork to the
main
branch of this repository. -
Provide a clear and detailed description of your changes in the PR.
-
Await feedback and be prepared to address any reviewer comments or requests for changes.
Once your PR is approved and merged, you will be credited for your contribution!
To fork the repository, click the "Fork" button at the top right of the GitHub page.
Before contributing, ensure you have the following prerequisites:
- CMake
- C++ Compiler (e.g., GCC)
- cURL library (for making HTTP requests)
Refer to the README.md for detailed setup instructions.
Follow the build instructions provided in the README.md file to build the project locally.
Please follow these coding guidelines when contributing:
- Follow the C++ Core Guidelines.
- Use meaningful variable and function names.
- Keep your code concise and well-documented.
- Format your code consistently.
Ensure that your changes do not break existing functionality. Write unit tests if necessary to validate your changes.
Write clear and concise commit messages following these guidelines:
- Use present tense ("Add feature" not "Added feature").
- Limit the first line to 72 characters or less.
- Include a brief and meaningful message about your changes.
- Reference relevant issues or PRs.
By contributing to this project, you agree that your contributions will be licensed under the MIT License.
Happy contributing!