To begin with, we are very thankful for your time and willingness to read this and contribute!

The following guideline should help you with suggesting changes to our project, so feel free to use it for your contribution. 😃

First of all, please check our Issues — this bug may have already been reported, and you just don`t need to spend your time on a new one.

If you haven`t found the relevant issue, don`t hesitate to create a new one, including as much detail as possible — the pre-made template will assist you in it.

In case you already have a PR with a solution, please remain so amazing and link it with the created issue.

Want a new feature or to change the existing one? We are very welcome your fresh ideas. 😃

Please create an issue with your proposal and describe your idea with full information about it. By adding some examples you also bring much happiness to our souls!

Give us some time to review your proposal and provide you with our feedback. It will be decided who is preparing the pull request: we may need your help or we will take care of it all. 🙂

Our team adheres to the defined requirements to coding style to optimize for readability. You can take a look on this Coding style guide to better understand what we expect to see in your code.

Please refer Developer guide to setup developer environment, build and run UTBot.

Currently, not all checks are automized. It's required to do manual testing after PR.