Captive Rubocop config

Rubocop shared configurations for projects

add the follow line into your Gemfile

group :test, :development do
  gem 'rubocop-config-captive', '~> 2.0'
end

And then in a terminal

$ bundle install
[...]

# /.rubocop.yml
inherit_gem:
  rubocop-config-captive:
    - config/default.yml
    # -OR-
    # - config/rubocop-XXX.yml

the configuration is very strict, it is normal to have many errors

bundle exec rubocop -a

bundle exec rubocop --auto-gen-config

Will create .rubocop_todo.yml will all non passing rules. It is advised to fix them later, rule by rule.

Each dependency should be explicitly set in the Gemfile and bundle update is strongly discouraged.

1. Install bundle-locker globally

gem install bundle-locker

2. Pin Gemfile using Gemfile.lock

bundle-locker ./Gemfile

3. Manually edit Gemfile and adjust constraints "x.x.x", "~> x.x.x", etc

4. Update Gemfile.lock

bundle install

To contribute, here are some inspirations for good configurations :

• Airbnb

MIT © Captive Studio julien.polo@captive.fr

rubocop-config-captive is maintained and funded by Captive. The names and logos for captive are trademarks of captive-studio.

We love open source software! See our other projects or hire us to design, develop, and grow your product.