Skip to content

fix rubocop config so CI does not scan vendored gems #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skunkworker merged 1 commit into from
Aug 27, 2026
Merged

fix rubocop config so CI does not scan vendored gems #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .rubocop.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
AllCops:
TargetRubyVersion: 3.1
# Do not adopt new cops automatically. Without this, every run prints the
# full pending cop list as a warning.
NewCops: disable
# Keep the default Exclude list. Without this, the Exclude below replaces the
# defaults, and RuboCop walks into vendor/bundle and reads the .rubocop.yml of
# every installed gem. Some of those name cops that no longer exist.
inherit_mode:
merge:
- Exclude
Exclude:
- 'gemfiles/**/*'

Expand Down
Loading