Effortless Code Conventions Review for Pull Request Changes
Reliably arranged source code helps hackability. You can filter code speedier if its organizing is predictable.
To fight with non-consistent source code formatting there are static analysis tools such as RuboCop.
We decided to share code formatting feedback directly on GitHub by commenting Pull Requests changes.
Our CircleCI 2.0 configuration to run pronto
NOTE: In order to reduce mess with dependencies we put all our linters and pronto into separate Gemfile.tools.
Finally, you need to add PRONTO_GITHUB_ACCESS_TOKEN. You could obtain your PERSONAL GITHUB ACCESS TOKEN by following this instruction and check environment variable on CircleCI to add it to the project.
There are similar ready SASS solutions to help you with reducing the amount of waste:
But they are not free and most of them are solve only specific problems.
With pronto, you have more options to customize by:
- setup specific code analyzers for the different problems
- easier support rules to follow company conventions
- store rules in the repository with project source code
Let’s remove the waste of time for trivial problems and spend it on codding!
Contact us to find out more about how we work. We’re excited to help you — as always, we’d love to hear what you think!