You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,25 @@ If the Cop is **only applicable for GitHub**, then this is the right place to pr
29
29
30
30
## For Maintainers
31
31
32
+
### Updating Rubocop Dependencies
33
+
34
+
Rubocop regularly releases new versions with new cops. We want to keep up to date with the latest Rubocop releases, and keep these rules and styleguide in sync to reduce burden on consumers of this gem.
35
+
36
+
- Run `bundle update rubocop rubocop-performance rubocop-rails` to update the dependencies within this repository. Major updates will require updating the `.gemspec` file because of the pinned version constraints.
37
+
- Run `bundle exec rubocop`, and copy the output of newly introduced rules into `config/default_pending.yml` and `config/rails_pending.yml`. They should look like this:
38
+
39
+
```sh
40
+
Lint/DuplicateMagicComment: # new in 1.37
41
+
Enabled: true
42
+
Style/OperatorMethodCall: # new in 1.37
43
+
Enabled: true
44
+
Style/RedundantStringEscape: # new in 1.37
45
+
Enabled: true
46
+
```
47
+
48
+
- Run `bundle exec rubocop` again to ensure that it runs cleanly without any pending cops. Also run `bundle exec rake` to run the tests.
49
+
- Work through the pending cops, and copy them to `config/{default,rails}.yml` with an explicity `Enabled: true` or `Enabled: false` depending on your decision as to whether they should be part of our standard ruleset.
50
+
32
51
### Releasing a new version
33
52
34
53
1. Update `rubocop-github.gemspec` with the next version number
0 commit comments