repokeeper 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c0a4d70fa1b1a42dc5e758970189a3f408a31adc
-  data.tar.gz: e74ab69c1261b64d1d5921a786e038994f60bd2a
+  metadata.gz: a49ed97e87f7255f8bbe21f395490f2e369fdfd0
+  data.tar.gz: ba9ba5fe84c2137c40fb00fb185f5ed9bd455071
 SHA512:
-  metadata.gz: 36053e57ea6d1c76041c608f15038e45e14f86d3d7614c5ea8c3d1c0bcc56889e6f8b498fa66951094a02f55c64d4b3eabd6d969a75a48a92fb3a7ee197f601a
-  data.tar.gz: 86677aa22199f03b20326a0be00e96ad99d7e9aea3fd4648914ff3ef36e493d3fc754f1ba5dfe07e7d1245e5afc1794e1c60443e7c4c098db2f93cc60b8ac834
+  metadata.gz: 37f17d9c968121f4b4cfab3f48f69fc1cb1109f894430238fb208115d0412f0fa460c0af81dbaf7fb6c30f390d8732bb2cefddda3cd8df1197658b4354198707
+  data.tar.gz: 855d32d62fc3bcf9786f0bf210d88a5e812071dbdc599601ee58428b7a09b7373f831d648f67657a99d98069a2302e49cde78dd5a448752e79073049d6999c82

data/README.md

@@ -1,14 +1,14 @@
 # Repokeeper
 
+[![Code Climate](http://img.shields.io/codeclimate/github/antlypls/repokeeper.svg?style=flat)](https://codeclimate.com/github/antlypls/repokeeper)
+[![Build Status](http://img.shields.io/travis/antlypls/repokeeper.svg?style=flat)](https://travis-ci.org/antlypls/repokeeper)
+[![Coverage Status](http://img.shields.io/coveralls/antlypls/repokeeper.svg?style=flat)](https://coveralls.io/r/antlypls/repokeeper)
+
 ## What's all this about?
 
 Repokeeper is a tool for git repositories analysis that highlights common
 flaws/bad practices in a workflow.
 
-## Flaws in workflow? What does it mean?
-
-Flaws commonly seen in repository management.
-
 ## Why do I need a tool for this?
 
 There are many tools for static code analysis like rubocop, flay, flog,
@@ -20,7 +20,6 @@ commits merged into master branch is a bad idea).
 By using Repokeeper, you can explore what was wrong in project's history, and
 then adjust your process accordingly.
 
-
 Problems with project management usually leave traces in repository history and
 structure.
 For instance, a rush in delivery of features to production can lead to debugging
@@ -97,6 +96,15 @@ from current directory even if it exists.
 If you are annoyed by tons of merge commits warnings, you can disable it,
 by `enabled: false` option in config file.
 
+## Can I specify which commits to analyze?
+
+By default repokeeper analyzes commits reachable from `HEAD`.
+But you can use `-r` option to specify revisions to analyze:
+
+* `-r rev1` analyze commits that are reachable from `rev1`
+* `-r rev1..rev2` analyze commits that are reachable from `rev2` but exclude
+  those that are reachable from `rev1`.
+
 ## More fun with custom formatters
 
 You can provide custom formatter class to change output the way you want,
@@ -170,14 +178,9 @@ And everything is ready to run:
 You know what to do.
 But don't forget to run `repokeeper` against your new commits ;)
 
+## Credits
 
-## Contact
-
-Anatoliy Plastinin
-
-- http://github.com/antlypls
-- http://twitter.com/antlypls
-- hello@antlypls.com
+Repokeeper is by [Anatoliy Plastinin](http://antlypls.com).
 
 ## License
 

data/lib/repokeeper/offenses/branches_offense.rb

@@ -1,6 +1,6 @@
 module Repokeeper
   module Offenses
-    class BranchesOffense < Struct.new(:branches, :message, :analyzer_name)
+    BranchesOffense = Struct.new(:branches, :message, :analyzer_name) do
       # we want Array(offense) to return [offense]
       undef_method :to_a
     end

data/lib/repokeeper/offenses/commit_offense.rb

@@ -1,6 +1,6 @@
 module Repokeeper
   module Offenses
-    class CommitOffense < Struct.new(:commit, :message, :analyzer_name)
+    CommitOffense = Struct.new(:commit, :message, :analyzer_name) do
       # we want Array(offense) to return [offense]
       undef_method :to_a
     end

data/lib/repokeeper/repo_analyzer.rb

@@ -30,7 +30,7 @@ module Repokeeper
     def enabled_analyzers(collection)
       collection
         .map { |analyzer_class| instantiate_analyzer(analyzer_class) }
-        .select { |analyzer| analyzer.enabled? }
+        .select(&:enabled?)
     end
 
     def enabled_commits_analyzers

data/lib/repokeeper/version.rb

@@ -1,3 +1,3 @@
 module Repokeeper
-  VERSION = '0.0.2'
+  VERSION = '0.0.3'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: repokeeper
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Anatoliy Plastinin
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-08-29 00:00:00.000000000 Z
+date: 2016-01-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rugged
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.21'
+        version: 0.21.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.21'
+        version: 0.21.0
 - !ruby/object:Gem::Dependency
   name: methadone
   requirement: !ruby/object:Gem::Requirement
@@ -123,7 +123,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.1
+rubygems_version: 2.4.7
 signing_key: 
 specification_version: 4
 summary: Repokeeper - git repo analysis tool