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: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
3
3
## Unreleased
4
4
5
-
- Unset `DisabledByDefault: true` in `config/default.yml`. This will use RuboCop's choice of default cops to enable, plus our existing augmentations in `config/default.yml`. Prevents confusing behaviour where downstream consumers didn't realise that RuboCop's default cops weren't being applied. (https://github.com/github/rubocop-github/pull/119)
5
+
- Unset `DisabledByDefault: true` in `config/default.yml`. Prevents confusing behaviour where users of the gem didn't realise that RuboCop's default cops weren't being applied (including potentially custom cops in their projects). We've explicitly set `Enabled: false` for all the cops that were previously default disabled. This has the effect that consumers of this gem won't be surprised by new linting violations when they use this new version in their projects. (https://github.com/github/rubocop-github/pull/119)
0 commit comments