Gusto's Ruby style guide implemented as RuboCop rules.
Add this line to your application's Gemfile:
gem 'rubocop-gusto', require: falseAnd then execute:
$ bundlerubocop-gusto ships with an executable that updates and maintains .rubocop.yml.
bundle exec rubocop-gusto initIf this is an existing project, it is recommended to run the autocorrector (bundle exec rubocop -a) and then to regenerate the .rubocop_todo.yml (bundle exec rubocop --auto-gen-config), so issues can be dealt with piecemeal.
To publish a new release:
- Update the
RuboCop::Gusto::VERSIONconstant to a higher version number conforming to this project's versioning policy. - Document your changes in the changelog.
- Open a pull request and follow the typical review/merge process.
- TODO: finish release process
After publishing, wait for dependabot, or make a new PR downstream to update to the latest version.
Submit new rules, updated configuration, and other checks to be used organization wide by submitting a Pull Request!
Rubocop-gusto generally follows semver, with the exception that the only thing that is considered a breaking change is a change in the public API to use rubocop-gusto.
Users can generally expect to need to regenerate their rubocop todo when they make a minor version bump to rubocop-gusto.
git config core.hooksPath script/githooks