|
| 1 | +# Contributing to solvecaptcha-php |
| 2 | + |
| 3 | +Thank you for considering contributing to the solvecaptcha-python! By contributing, you're helping improve the project and enabling others to benefit from your improvements. |
| 4 | + |
| 5 | +Here are a few guidelines to help you get started. |
| 6 | + |
| 7 | +## How to Contribute |
| 8 | + |
| 9 | +1. **Fork the repository** |
| 10 | + If you'd like to contribute, please start by forking the project and cloning it to your local machine. |
| 11 | + |
| 12 | + ```bash |
| 13 | + git clone https://github.com/solvercaptcha/solvecaptcha-php.git |
| 14 | + ``` |
| 15 | + |
| 16 | +2. **Create a new branch** |
| 17 | + Create a new branch for your feature or bug fix. This will help keep your changes separate from the main codebase. |
| 18 | + |
| 19 | + ```bash |
| 20 | + git checkout -b my-feature-branch |
| 21 | + ``` |
| 22 | + |
| 23 | +3. **Make your changes** |
| 24 | + Modify the code or documentation as needed. Make sure to follow the project's coding style and conventions. |
| 25 | + |
| 26 | +4. **Test your changes** |
| 27 | + Ensure that your changes work as expected and do not break anything in the project. If applicable, write tests to cover your changes. |
| 28 | + |
| 29 | +5. **Commit your changes** |
| 30 | + After you've made your changes, commit them with a meaningful message describing what you've done. |
| 31 | + |
| 32 | + ```bash |
| 33 | + git commit -m "Add feature X to bypass challenge" |
| 34 | + ``` |
| 35 | + |
| 36 | +6. **Push your changes** |
| 37 | + Push your changes to your forked repository. |
| 38 | + |
| 39 | + ```bash |
| 40 | + git push origin my-feature-branch |
| 41 | + ``` |
| 42 | + |
| 43 | +7. **Submit a pull request** |
| 44 | + Navigate to the original repository and submit a pull request. Describe the changes you've made and why they're important. |
| 45 | + |
| 46 | + We will review your pull request and get back to you as soon as possible! |
| 47 | + |
| 48 | +## Reporting Issues |
| 49 | + |
| 50 | +If you find any bugs or issues with the project, feel free to open an issue in the **Issues** tab. When reporting an issue, please provide the following information: |
| 51 | + |
| 52 | +- A detailed description of the issue. |
| 53 | +- Steps to reproduce the issue. |
| 54 | +- Any relevant error messages or logs. |
| 55 | + |
| 56 | +## Code of Conduct |
| 57 | + |
| 58 | +By contributing to this project, you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md). Please be respectful and considerate to other contributors. |
| 59 | + |
| 60 | +## Types of Contributions |
| 61 | + |
| 62 | +Here are some ways you can contribute to the project: |
| 63 | + |
| 64 | +- **Bug Fixes**: If you find a bug, feel free to submit a pull request with a fix. |
| 65 | +- **Feature Requests**: Have a great idea for a new feature? Open an issue to discuss it! |
| 66 | +- **Documentation**: Help improve the documentation or add new guides to make the project more accessible to others. |
| 67 | +- **Tests**: Ensure that the project is thoroughly tested and improve the test coverage. |
| 68 | +- **Code Refactoring**: Help improve the project codebase by refactoring or optimizing the code. |
| 69 | + |
| 70 | +## Thank You! |
| 71 | + |
| 72 | +Your contributions are greatly appreciated! Together, we can make this project even better for everyone. |
0 commit comments