We want to start off by saying thank you for contributing to Claudy 🙏 This project is a labor of love, and we appreciate all of you that take care of new features, catch bugs, make performance improvements, and help with documentation. Every contribution is meaningful, so thank you for participating. That being said, here are a few guidelines that we ask you to follow so we can successfully address your issue.
When contributing to this repository, please first discuss the change you wish to make via a GitHub issue with the owners of this repository before making a change. Michael is reachable at it@les4sources.be and will find a way to chat with you easily.
Please note we have a Code of Conduct, please follow it in all your interactions with the project.
-
If you have any questions about Claudy, search the wiki first.
-
If you find a security bug, DO NOT submit an issue here. Please send an e-mail to it@les4sources.be instead.
-
Do a small search on the issues tracker before submitting your issue to see if it was already reported or fixed. In case it was not, create a bug report. If you are getting exceptions, please include the full backtrace.
That's it! The more information you give, the more easy it becomes for us to track it down and fix it. Ideal scenario would be adding the issue to the Claudy test suite or to a sample application.
Thanks!