commit_format 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ef4ace94c6a11e7172e7013ce1eebbccd4ab41e26d3e926b109f10af2e69bf39
-  data.tar.gz: b314bbcc2b661def7c107cf3ea2ea6d0d129695348618fefb9af79b1a20b3224
+  metadata.gz: 68d7c9f7d1e0c01f028da842d66ccce4fb35b24e867cd6a813d31d6bf2146503
+  data.tar.gz: 901660bfa3f3794ae6f58a7d17f552a2e5e07386dbd5cf9ba9c425b60d77a83c
 SHA512:
-  metadata.gz: 14701063826fe6467c185353da71aeb2bf7b92fe01fc94e34a1e4aa7f4ef6169e3b6f1f3f78b16113c81928eaf2f263d7183be38cf0d56564da099e84fdcd4b7
-  data.tar.gz: c6b176440cfc56cab8003151c41bf940f6ce67879ea7298827847c65eb6d5ad9b86eaf55c1a7b5e283571e55ee08c32f6deddd737622c2aa159b5ddb9782b88b
+  metadata.gz: b142b8f0a27079b93a7a2c8621a755d948120d06099bc3c1f514a157633bd6eabedc66751b67d205bf3761899d61b042461497c22169e0178a930c79a9404dc0
+  data.tar.gz: c2aaa0b482a4e97c6741a8d9f12b5ca779d3b26c135f4f7a2352d9c1f4cc07997157102a6eae1c63d77ff786e116513b9c39017fab6aa750b99d87d9e755c068

data/CHANGELOG.md

@@ -1,5 +1,32 @@
 # Commit Format
 
+## 0.2.0
+
+### Added
+
+- [5c3aed6](https://github.com/tombruijn/commit-format/commit/5c3aed6b4d4610842fbf57e7b4fede06283c6bba) minor - Add paragraph flag to format message body output to join paragraph lines. This is similar to how GitHub now formats Pull Requests with a single commit. Use `-p`/`--paragraph` to use this feature.
+  
+  Given a commit with the message body of two lines:
+  
+  ```
+  Line 1.
+  Line 2.
+  
+  - Item 1.
+  - Item 2.
+  ```
+  
+  This is output as:
+  
+  ```
+  Line 1. Line 2.
+  
+  - Item 1.
+  - Item 2.
+  ```
+  
+  Other Markdown syntax, like tables, lists, code blocks, etc. are all kept in their original format in the output. Their lines are not joined into one line.
+
 ## 0.1.0
 
 Initial release.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[tom@tomdebruijn.com](mailto:tom@tomdebruijn.com).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/README.md

@@ -29,6 +29,10 @@ commit-format -n 5
 # Print all new commits since selected base branch
 commit-format -b main
 commit-format -b feature-branch
+
+# Print all commits with text lines joined into a paragraph
+commit-format --paragraph
+commit-format -p
 ```
 
 ## Features
@@ -36,6 +40,17 @@ commit-format -b feature-branch
 - Turns each commit subject into a markdown heading.
 - Indents all headings in the message body on level lower. Heading level 2
   becomes heading level 3, etc.
+- Join text lines together as continuous paragraphs for easier reading in Pull
+  Requests. Markdown syntax like code block, blockquotes, lists, tables, etc.
+  are all kept in their original format.
+  ```
+  # For example:
+  A commit message with multiple text lines
+  across multiple lines.
+
+  # Becomes
+  A commit message with multiple text lines across multiple line.
+  ```
 
 ## Development
 

data/commit_format.gemspec

@@ -28,7 +28,7 @@ Gem::Specification.new do |gem|
     "source_code_uri" => "https://github.com/tombruijn/commit-format"
   }
 
-  gem.add_development_dependency "pry", "0.14.1"
+  gem.add_development_dependency "debug", "1.6.2"
   gem.add_development_dependency "rspec", "3.10.0"
   gem.add_development_dependency "rubocop", "1.25.0"
 end

data/lib/commit_format/cli.rb

@@ -12,7 +12,11 @@ module CommitFormat
       parser = Parser.new(@args)
       commits = parser.commits
 
-      formatter = Formatter.new(commits)
+      formatter =
+        Formatter.new(
+          commits,
+          :paragraph => @args.fetch(:paragraph, false)
+        )
       formatted_commits = formatter.formatted_commits
       print_formatted_commits(formatted_commits)
     end
@@ -31,10 +35,17 @@ module CommitFormat
 
     def parse_args(args) # rubocop:disable Metrics/MethodLength
       options = {}
-      OptionParser.new do |parser|
+      OptionParser.new do |parser| # rubocop:disable Metrics/BlockLength
         document_cli(parser)
 
         parser.separator "Options:"
+        parser.on(
+          "-p",
+          "--paragraph",
+          "Join paragraph lines into one line"
+        ) do |paragraph|
+          options[:paragraph] = paragraph
+        end
         parser.on(
           "-n",
           "--max-count <number>",

data/lib/commit_format/formatter.rb

@@ -2,16 +2,34 @@
 
 module CommitFormat
   class Formatter
-    def initialize(commits)
+    def initialize(commits, options = {})
       @commits = commits
+      @paragraph = options[:paragraph]
     end
 
     def formatted_commits
-      @commits.map { |commit| format_commit(commit) }
+      @commits.map do |commit|
+        if @paragraph
+          format_commit_as_paragraphs(commit)
+        else
+          format_commit(commit)
+        end
+      end
     end
 
     private
 
+    def format_commit_as_paragraphs(commit)
+      message = Message.new
+      lines = commit.split("\n")
+      subject = "## #{lines.shift}\n"
+      lines.each do |line|
+        message.line line
+      end
+      message.end!
+      "#{subject}#{message}"
+    end
+
     def format_commit(commit)
       formatted_commit =
         commit.lines.map do |line|
@@ -25,5 +43,114 @@ module CommitFormat
       # Start subject with a heading
       "## #{formatted_commit}"
     end
+
+    class Message
+      def initialize
+        @lines = []
+        @paragraph = []
+        @code_block = false
+      end
+
+      def line(string) # rubocop:disable Metrics/MethodLength, Metrics/CyclomaticComplexity, Metrics/PerceivedComplexity
+        if code_block_fence?(string)
+          new_paragraph
+          code_block!
+          lines << string
+          return
+        elsif code_block?
+          lines << string
+          return
+        elsif string.empty? # Line break
+          new_paragraph
+          line_break
+          return
+        elsif string.start_with? "#"
+          write_paragraph
+          heading string
+          return
+        elsif fixed_line?(string)
+          new_paragraph
+          lines << string
+          return
+        elsif heading_line?(string)
+          write_paragraph
+          lines << string
+          return
+        end
+
+        paragraph << string
+        # Line with line break and the end
+        write_paragraph if string.end_with? "  "
+      end
+
+      def end!
+        write_paragraph
+      end
+
+      def to_s
+        @lines.join("\n")
+      end
+
+      private
+
+      LINE_BREAK = ""
+
+      attr_reader :lines, :paragraph
+
+      def new_paragraph
+        write_paragraph if paragraph.any?
+      end
+
+      def write_paragraph
+        return unless paragraph.any?
+
+        lines << paragraph.join(" ")
+        clear_paragraph!
+      end
+
+      def heading(string)
+        lines << "##{string}"
+      end
+
+      HEADING_LINE_CHARS = ["=", "-"].freeze
+
+      def heading_line?(string)
+        line = string.strip
+        uniq_chars = line.chars.uniq
+        return false if uniq_chars.length > 1
+
+        HEADING_LINE_CHARS.include?(uniq_chars.first)
+      end
+
+      def fixed_line?(string)
+        string.start_with?("  ") || # Indented line
+          string.start_with?("\t") || # Indented line
+          string.start_with?("- ") || # Unordered list item
+          string.start_with?("* ") || # Unordered list item
+          string.start_with?("|") || # Table
+          string.start_with?("> ") || # Blockquote
+          string.start_with?(/\d+\. /) # Numbered list item
+      end
+
+      def clear_paragraph!
+        @paragraph = []
+      end
+
+      def code_block?
+        @code_block
+      end
+
+      def code_block!
+        @code_block = !@code_block
+      end
+
+      def code_block_fence?(string)
+        string.start_with?("```") || string.start_with?("~~~")
+      end
+
+      def line_break
+        lines << LINE_BREAK
+      end
+    end
   end
 end

data/lib/commit_format/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module CommitFormat
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

data/spec/lib/commit_format/cli_spec.rb

@@ -4,7 +4,7 @@ RSpec.describe CommitFormat::Cli do
   describe "with --version flag" do
     it "prints the version number" do
       output = run_version
-      expect(output).to eql(CommitFormat::VERSION)
+      expect(output.strip).to eql(CommitFormat::VERSION)
     end
   end
 
@@ -31,6 +31,374 @@ RSpec.describe CommitFormat::Cli do
         Second line.
       OUTPUT
     end
+
+    it "indents headings by one level" do
+      test_dir = "indent_headings"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2", <<~MESSAGE
+          Commit message body.
+          Second line.
+
+          ## Heading 2
+
+          Hello heading.
+          Other line.
+        MESSAGE
+      end
+
+      output = run(test_dir)
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body.
+        Second line.
+
+        ### Heading 2
+
+        Hello heading.
+        Other line.
+      OUTPUT
+    end
+  end
+
+  describe "with --paragraph flag" do
+    it "formats all commits to main branch as paragraphs" do
+      test_dir = "paragraph_flag"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+      OUTPUT
+    end
+
+    it "indents headings by one level" do
+      test_dir = "paragraph_flag_headings"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+
+            ## Heading 2
+
+            Hello heading.
+            ## Heading 2
+            Other line.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        ### Heading 2
+
+        Hello heading.
+        ### Heading 2
+        Other line.
+      OUTPUT
+    end
+
+    it "keeps underline heading formatting" do
+      test_dir = "paragraph_flag_headings_underline"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+
+            Heading 2
+            ---
+
+            End of message.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body.
+
+        Heading 2
+        ---
+
+        End of message.
+      OUTPUT
+    end
+
+    it "keeps indented lines" do
+      test_dir = "paragraph_flag_indented"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+
+              Hello code.
+              Other line.
+
+            Paragraph line.
+
+            \tNew indented
+            \tblock.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body.
+
+          Hello code.
+          Other line.
+
+        Paragraph line.
+
+        \tNew indented
+        \tblock.
+      OUTPUT
+    end
+
+    it "starts a new line after a line ending with two spaces" do
+      test_dir = "paragraph_flag_end_spaces"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2", <<~MESSAGE, :verbatim => true
+          Commit message body.
+          Second line.
+
+          Start line.
+          Hello line.\x20\x20
+          Next line.
+
+          Footer
+        MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        Start line. Hello line.\x20\x20
+        Next line.
+
+        Footer
+      OUTPUT
+    end
+
+    it "keeps list formatting" do
+      test_dir = "paragraph_flag_lists"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+
+            - Hello list.
+              Other line.
+            - Test
+            * Second item.
+              * Third item.
+
+            1. First item.
+            2. Second item.
+              1. Third item.
+            - End list
+
+            Footer
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        - Hello list.
+          Other line.
+        - Test
+        * Second item.
+          * Third item.
+
+        1. First item.
+        2. Second item.
+          1. Third item.
+        - End list
+
+        Footer
+      OUTPUT
+    end
+
+    it "keeps tables formatting" do
+      test_dir = "paragraph_flag_tables"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+
+            | Heading 1 | Heading 2 |
+            | --------- |:---------:|
+            | lorem     | lorem     |
+            | lorem     | lorem     |
+            | lorem     | lorem     |
+
+            Footer
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        | Heading 1 | Heading 2 |
+        | --------- |:---------:|
+        | lorem     | lorem     |
+        | lorem     | lorem     |
+        | lorem     | lorem     |
+
+        Footer
+      OUTPUT
+    end
+
+    it "keeps blockquotes formatting" do
+      test_dir = "paragraph_flag_blockquotes"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+
+            > I am a quote
+            > I am another quote
+
+            > Second quote
+
+            Footer
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        > I am a quote
+        > I am another quote
+
+        > Second quote
+
+        Footer
+      OUTPUT
+    end
+
+    it "keeps code blocks formatting" do
+      test_dir = "paragraph_flag_code_blocks"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+            Second line.
+
+            ```ruby
+            Hello code.
+            # Comment line
+            Other line.
+            ```
+
+            ~~~ruby
+            Hello code.
+            Other line.
+            ~~~
+
+            New paragraph.
+            With new line.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body. Second line.
+
+        ```ruby
+        Hello code.
+        # Comment line
+        Other line.
+        ```
+
+        ~~~ruby
+        Hello code.
+        Other line.
+        ~~~
+
+        New paragraph. With new line.
+      OUTPUT
+    end
+
+    it "keeps horizontal line formatting" do
+      test_dir = "paragraph_flag_horizontal_line"
+      prepare_repository test_dir do
+        create_commit "Commit subject 1", "Commit message body.\nSecond line."
+        checkout_branch "my-branch"
+        create_commit "Commit subject 2",
+          <<~MESSAGE
+            Commit message body.
+
+            ---
+
+            New paragraph.
+          MESSAGE
+      end
+
+      output = run(test_dir, ["--paragraph"])
+      expect(output).to eql(<<~OUTPUT)
+        ## Commit subject 2
+
+        Commit message body.
+
+        ---
+
+        New paragraph.
+      OUTPUT
+    end
   end
 
   context "with --base-branch argument" do
@@ -198,8 +566,6 @@ RSpec.describe CommitFormat::Cli do
   end
 
   def run_version
-    capture_stdout do
-      CommitFormat::Cli.new(["--version"]).execute
-    end
+    `bin/commit-format --version`
   end
 end

data/spec/support/repository_helper.rb

@@ -28,7 +28,9 @@ module RepositoryHelper
     `git checkout -b "#{name}"`
   end
 
-  def create_commit(subject, message)
-    `git commit --allow-empty -m "#{subject}" -m "#{message}"`
+  def create_commit(subject, message, verbatim: false)
+    options = []
+    options << "--cleanup verbatim" if verbatim
+    `git commit --allow-empty -m "#{subject}" -m '#{message}' #{options.join(" ")}`
   end
 end

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: commit_format
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Tom de Bruijn
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-01-23 00:00:00.000000000 Z
+date: 2022-09-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: pry
+  name: debug
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.14.1
+        version: 1.6.2
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.14.1
+        version: 1.6.2
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -67,6 +67,7 @@ files:
 - ".rubocop.yml"
 - ".semaphore/semaphore.yml"
 - CHANGELOG.md
+- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE
 - README.md
@@ -107,7 +108,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.4
+rubygems_version: 3.3.22
 signing_key:
 specification_version: 4
 summary: Git commit formatter utility.