Sourcery AI

@giorgi_beria thank you!

@aboutphilippe Thanks a lot. :-) We're curious about your feedback both to Sourcery and to the Getting Started docs. https://docs.sourcery.ai/Guides/...

@m_h_lines definitely! I just connected with you on LinkedIn, but let me know if there's a better way to get in touch

@tex_dworkin Thank you!

@shushant_lakhyani Thanks a lot.

@tjamesjones good question! You can handle legacy code in two ways: 1. Do a full project review to identify all existing issues. We recommend doing this with our command line interface (https://docs.sourcery.ai/Guides/...). You can run `sourcery review ` to check all of your existing code and get a baseline for what issues you have. You can then choose which of those you want to fix right away and which you want to wait to deal with. 2. Set up Sourcery in your CI (https://docs.sourcery.ai/Guides/...) or as a pre-commit hook (https://docs.sourcery.ai/Guides/...) and set it to only review changed code using the --diff option. Then Sourcery will only look at the changed code and only suggest changes on those.

@tim_sourcery yes thanks that makes sense

@rishabh_agrawal2 Good question. SonarQube is also a great code quality tool. There's an overlap between their functionalities, but there are also some differences. 1) Automated fixes Sourcery provides automated fixes for more than 100 common code quality issues. You can apply these immediately in your IDE as you type. Or you can fix dozens of issues at once in the command line. https://docs.sourcery.ai/Guides/...

@rishabh_agrawal2 2) Custom rules With Sourcery, you can define your own rules specific to your codebase. For example: * Check the dependencies between the packages of your project. * Project specific naming conventions. * Getting rid of deprecated code https://docs.sourcery.ai/Guides/... https://docs.sourcery.ai/Guides/...