Daniel Colson 087e0ccb72 Add RuboCop for `assert_not` over `assert !` ... We added `assert_not` in f75addd "to replace warty 'assert !foo'". fa8d35b agrees that it is warty, and so do I. This custom Rubocop rule turns the wart into a violation. As with my last custom cop, https://github.com/rails/rails/pull/32441, I want to make sure this looks right on code climate before pushing another commit to autocorrect everything. @toshimaru I just noticed https://github.com/toshimaru/rubocop-rails/pull/26 Is there a better way to add these custom cops, or were you saying we shouldn't have custom cops at all?		2018-04-19 08:11:28 -04:00
..
custom_cops	Add RuboCop for `assert_not` over `assert !`	2018-04-19 08:11:28 -04:00
qunit-selenium-runner.rb	Fix ActionView UJS build	2018-01-18 11:28:12 -05:00
travis.rb	Only run isolated tests on the latest stable ruby: that's now 2.5	2018-01-25 09:55:10 +10:30