feat: add release rule for revert commits

If a revert commit is analyzed (without the reverted commit being part of the commit group) it will now trigger a `patch` release by default.

lib/analyze-commit.js

@@ -15,9 +15,11 @@ module.exports = (releaseRules, commit) => {
 
   releaseRules
     .filter(
-      ({breaking, release, ...rule}) =>
+      ({breaking, revert, release, ...rule}) =>
         // If the rule is not `breaking` or the commit doesn't have a breaking change note
         (!breaking || (commit.notes && commit.notes.length > 0)) &&
+        // If the rule is not `revert` or the commit is not a revert
+        (!revert || commit.revert) &&
         // Otherwise match the regular rules
         isMatchWith(
           commit,

lib/default-release-rules.js

@@ -5,6 +5,7 @@
  */
 module.exports = [
   {breaking: true, release: 'major'},
+  {revert: true, release: 'patch'},
   // Angular
   {type: 'feat', release: 'minor'},
   {type: 'fix', release: 'patch'},

test/analyze-commit.test.js

@@ -9,6 +9,14 @@ test('Match breaking change', t => {
   t.is(analyzeCommit([{breaking: true, release: 'major'}], commit), 'major');
 });
 
+test('Match revert commit', t => {
+  const commit = {
+    revert: {header: 'Update: First feature', hash: '123'},
+  };
+
+  t.is(analyzeCommit([{revert: true, release: 'patch'}], commit), 'patch');
+});
+
 test('Match multiple criteria with breaking change', t => {
   const commit = {
     type: 'feat',
@@ -18,6 +26,15 @@ test('Match multiple criteria with breaking change', t => {
   t.is(analyzeCommit([{type: 'feat', breaking: true, release: 'major'}], commit), 'major');
 });
 
+test('Match multiple criteria with revert', t => {
+  const commit = {
+    type: 'feat',
+    revert: {header: 'Update: First feature', hash: '123'},
+  };
+
+  t.is(analyzeCommit([{type: 'feat', revert: true, release: 'major'}], commit), 'major');
+});
+
 test('Match multiple criteria', t => {
   const commit = {type: 'feat', scope: 'test'};