mirror of
https://github.com/openfoodfoundation/openfoodnetwork
synced 2026-02-04 22:16:08 +00:00
8f79fe2768
We configured Code Climate to be aware of all open issues instead of ignoring open issues via the rubocop todo lists. We were hoping that Code Climate could give us some nice stats like progress if it's aware of all our open issues. But the graphs don't tell us anything. So it's better to have one source of truth for our open style issues and that is our rubocop config in this repository. It contains two todo lists that document all violations we would like to fix in the future but it's okay to submit pull requests that don't fix those. Instead of accepting new style issues in Code Climate, every pull request with new violations has to add them to the rubocop config. I hope that this will make rubocop more useful and encourage developers to reduce code style debt.
22 lines
659 B
YAML
22 lines
659 B
YAML
# This is our main Rubocop configuration for developers. It is used when you run:
|
|
#
|
|
# bundle exec rubocop
|
|
#
|
|
# The configuration is split into three files. Look into those files for more details.
|
|
#
|
|
require: rubocop-rails
|
|
inherit_from:
|
|
|
|
# The automatically generated todo list to ignore all current violations.
|
|
- .rubocop_todo.yml
|
|
|
|
# Our Open Food Network style guide. If you want to see all violations,
|
|
# then use only that configuration:
|
|
#
|
|
# bundle exec rubocop -c .rubocop_styleguide.yml
|
|
#
|
|
- .rubocop_styleguide.yml
|
|
|
|
# A manually compiled todo list to ignore metrics violations on a file-by-file basis.
|
|
- .rubocop_manual_todo.yml
|