-
Do not open up a GitHub issue if the bug is a security vulnerability in EasyCurl, just sent me an e-mail about this problem.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of EasyCurl will generally not be accepted.
- Suggest your change in the issues marked with the label "enhancement" and start writing code.
- Ask any question about how to use EasyCurl in the issues marked with the label "question".
Thanks!
❤️ ❤️ ❤️