git-lint 2.3.1 → 2.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 179a706a6991b40dbbb489fdb38fb955505f0ee1c93f866a703e711a6979f8c6
-  data.tar.gz: 5233c41ef4e4862ed4baaa7ceb354deb8e7dbe69efb90720c888ae92628cc7b1
+  metadata.gz: 2738d9812647c24090cf0465db57379709af0fd64c9c8aa474f7d68c2f7896f5
+  data.tar.gz: f258c1a530ce3faf4f115feb2a108d021f09959eda092be58d92b75b8b5862d6
 SHA512:
-  metadata.gz: 6e0d44179f5b348ab65ecf01a5b252726940b3e1eda0a5659d63d9a15755e6ea6f3e940d6d3445339b4a0d1541f89ba279789ecfa127770d5f02927c2533b6eb
-  data.tar.gz: eb86f245720675fff023b44b90e634d91337a53f15af18cacf4f458825c48a57501f054260e2fc4bb75c208e7579ecdb79f81f89008830f02fa16e9059f7ddaa
+  metadata.gz: 44551a125b11785cdadbb3d65e63c049e2a513704ebef7f21419c95b21c396ac8f2193bd7f2bf35d4f30469789236b793a3cd1f2a3554efc715b0ebcaa4621e4
+  data.tar.gz: d6f8299c1c864fe7cfde0a692119b3bab8f1450ce89df534b76ac3c84d31cb54576cc2a45f300fdb8afd3cdfbd539f029aab88967e0bc7184ec9a4a0c8a01396

data.tar.gz.sig

@@ -1,2 +1,3 @@
-F���ㅺ��_J���YO�TN�0U
-���V���s�� 4������8�c���Z��&�Ĝx����7|��s������x��cqP7ǯ��b[X�>�HT�,�`��#!9�j~R�*UNݯ�RY�wBE��%_7��_=q
+_f�
+s:��v:��~���.�3if�J��^Al�N8�M0��4�QdE����D�$����;"��tzt��ǃ�$�ݒS���~
fƮv�V���$!V�������.n�L�f�?
+"f~l����v��:���s!��a��b��y�h̜�H�1����d	e�]
�g�#�N�M8#�/���VP:KD!SJE��܏��͓�n20�5i�HU;�F���H[ȑ����		��]�V�d?!Kj�

data/README.adoc

@@ -731,12 +731,12 @@ Automatically ignores _fixup!_ or _squash!_ commit prefixes when calculating sub
 | true    | error    | includes: (see below)
 |===
 
-Ensures the commit subject uses consistent prefixes that explain _what_ is being committed. The
+Ensures each commit subject uses consistent prefixes that explain _what_ is being committed. The
 `includes` are _case sensitive_ and default to the following prefixes:
 
 * *Fixed* - Identifies what was fixed. The commit should be as small as possible and consist of
-  changes to implementation and spec only. In some cases this might be a single line or file change.
-  The important point is the change is applied to existing code which corrects behavior that wasn't
+  changes to implementation and spec only. In some cases this might be a single line change. The
+  important point is the change is applied to existing code which corrects behavior that wasn't
   properly implemented earlier.
 * *Removed* - Identifies what was removed. The commit should be as small as possible and consist
   only of removed lines/files from the existing implementation. This might also mean breaking
@@ -754,14 +754,17 @@ Ensures the commit subject uses consistent prefixes that explain _what_ is being
   implementation behavior or corresponding specs because, if that happens, then one of the other
   four prefixes is what you want to use instead.
 
-In practice, using a prefix other than what has been detailed above to explain _what_ is being
-committed is never needed. These prefixes are not only short and easy to remember but also have the
+In practice, it is quite rare to need a prefix other than what has been detailed above to explain
+_what_ is being committed. These prefixes are not only short and easy to remember but also have the
 added benefit of categorizing the commits for building release notes, change logs, etc. This becomes
-handy when coupled with another tool, link:https://www.alchemists.io/projects/milestoner[Milestoner],
-for producing consistent project milestones and Git tag histories.
-
-💡 Automatically ignores _amend!_, _fixup!_, or _squash!_ commit prefixes when used as a Git Hook in
-order to not disturb interactive rebase workflows.
+handy when coupled with another tool,
+link:https://www.alchemists.io/projects/milestoner[Milestoner], for producing consistent project
+milestones and Git tag histories. For a deeper dive on subject prefixes and good commit messages in
+general, please read about link:https://www.alchemists.io/articles/git_commit_anatomy[commit anatomy
+] to learn more. 🎉
+
+💡 This analyzer automatically ignores _amend!_, _fixup!_, or _squash!_ commit prefixes when used as
+a Git Hook in order to not disturb interactive rebase workflows.
 
 === Commit Subject Suffix
 

data/lib/git/lint/cli.rb

@@ -78,7 +78,7 @@ module Git
         else
           help "--hook"
         end
-      rescue Errors::Base, GitPlus::Errors::Base => error
+      rescue Errors::Base, GitPlus::Error => error
         abort colorizer.red("#{Identity::LABEL}: #{error.message}")
       end
 

data/lib/git/lint/identity.rb

@@ -6,7 +6,7 @@ module Git
     module Identity
       NAME = "git-lint"
       LABEL = "Git Lint"
-      VERSION = "2.3.1"
+      VERSION = "2.3.2"
       VERSION_LABEL = "#{LABEL} #{VERSION}"
     end
   end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: git-lint
 version: !ruby/object:Gem::Version
-  version: 2.3.1
+  version: 2.3.2
 platform: ruby
 authors:
 - Brooke Kuhlmann
@@ -28,7 +28,7 @@ cert_chain:
   lkHilIrX69jq8wMPpBhlaw2mRmeSL50Wv5u6xVBvOHhXFSP1crXM95vfLhLyRYod
   W2A=
   -----END CERTIFICATE-----
-date: 2021-07-11 00:00:00.000000000 Z
+date: 2021-08-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: git_plus
@@ -36,14 +36,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.5'
+        version: '0.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.5'
+        version: '0.6'
 - !ruby/object:Gem::Dependency
   name: pastel
   requirement: !ruby/object:Gem::Requirement
@@ -186,7 +186,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.23
+rubygems_version: 3.2.25
 signing_key:
 specification_version: 4
 summary: A command line interface for linting Git commits.