rubocop-bitcrowd 1.0.0 → 1.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.rubocop.yml +0 -2
- data/README.md +2 -8
- data/rubocop-bitcrowd.gemspec +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3ff6583cf1514e446608ebbe8335029a0d68e44f
|
|
4
|
+
data.tar.gz: 74c35f5d12ccb77539a0a1dc270d695145e54a47
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e7a870325434917136503ae5ce084c49724cfd63b20429e19a40eb1285cf1aaa33837f7f32652ba445b4be7d22cd8c588a71ab8b754fcbfb88a5296d346071f5
|
|
7
|
+
data.tar.gz: f14c85911f999cab6e4bc944eb27e7f77e9a556d7f3af18739a4bfd02faf53d2d0a79deb305f8e078376f47843934fc24c308f408b22de0f34f3ef5133fceb95
|
data/.rubocop.yml
CHANGED
data/README.md
CHANGED
|
@@ -45,15 +45,9 @@ fixable Cop into a single commit when initially adding rubocop into a bigger pro
|
|
|
45
45
|
This gem provides a simple script, that can help you with this task:
|
|
46
46
|
|
|
47
47
|
1. Create your rubocop configuration (either with the instructions above or your own)
|
|
48
|
-
2. Create a rubocop_todo.yml with:
|
|
49
|
-
```
|
|
50
|
-
rubocop --auto-gen-config
|
|
51
|
-
```
|
|
48
|
+
2. Create a rubocop_todo.yml with: `rubocop --auto-gen-config`
|
|
52
49
|
3. Make sure you have a clean state in git, since the script will make commits for you (you may want to commit your rubocop_todo.yml)
|
|
53
|
-
4. Run the script (may take a while, when you want to continue working on your project meanwhile run this in a separate checkout):
|
|
54
|
-
```
|
|
55
|
-
rubocop-autofix
|
|
56
|
-
```
|
|
50
|
+
4. Run the script (may take a while, when you want to continue working on your project meanwhile run this in a separate checkout): `rubocop-autofix`
|
|
57
51
|
5. Review all commits made by the script and run your tests. You can now drop certain commits of cops you don't want. Often it may make some sense to run the script again with changed settings, since rebasing 100+ commits is no fun.
|
|
58
52
|
|
|
59
53
|
|
data/rubocop-bitcrowd.gemspec
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: rubocop-bitcrowd
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.1.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- bitcrowd
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2017-
|
|
11
|
+
date: 2017-05-08 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|
|
@@ -90,7 +90,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
90
90
|
version: '0'
|
|
91
91
|
requirements: []
|
|
92
92
|
rubyforge_project:
|
|
93
|
-
rubygems_version: 2.
|
|
93
|
+
rubygems_version: 2.5.2
|
|
94
94
|
signing_key:
|
|
95
95
|
specification_version: 4
|
|
96
96
|
summary: The bitcrowd rubocop.yml as a gem.
|