(GH-134) Add new config options

Author: gep13

docs/input/docs/configuration/default-configuration.md

@@ -14,6 +14,9 @@ create:
   footer-content:
   footer-includes-milestone: false
   milestone-replace-text:
+  include-sha-section: false
+  sha-section-heading: "SHA256 Hashes of the release artifacts"
+  sha-section-line-format: "- `{1}\t{0}`"
 export:
   include-created-date-in-title: false
   created-date-string-format:
@@ -38,31 +41,31 @@ Not all options are required.  For example, footer-content, is an empty string b
 
 When creating a Release, there are a number of options which can be set to control the look and feel of the generated release notes.
 
-  * **include-footer**
-    * A boolean value which indicates that a footer should be included within the release notes.  Default is false.
-  * **footer-heading**
-    * A string value which contains the heading text for the footer.  Default is an empty string.
-  * **footer-content**
-    * A string value which contains the main body text for the footer.  This can be anything.  A typical example might be to provide information about where the release can be installed from.  Default is an empty string.
-  * **footer-includes-milestone**
-    * A boolean value which indicates that the footer content contains a milestone, which should be replaced with the actual milestone value.  As an example, let's say you want to provide a link to where you can download your release, and the URL could be something like http://mydomain.com/releases/0.1.0.  You don't want to have to hard code the milestone number into your yaml configuration, so instead, you can use a replacement string in your footer-content, which will then be replaced with the actual milestone release number, when the release is created.  Default is false.
-  * **milestone-replace-text**
-    * A string value which contains the string which should be replaced in the footer-content with the actual milestone release number. Default is an empty string.
+* **include-footer**
+  * A boolean value which indicates that a footer should be included within the release notes.  Default is false.
+* **footer-heading**
+  * A string value which contains the heading text for the footer.  Default is an empty string.
+* **footer-content**
+  * A string value which contains the main body text for the footer.  This can be anything.  A typical example might be to provide information about where the release can be installed from.  Default is an empty string.
+* **footer-includes-milestone**
+  * A boolean value which indicates that the footer content contains a milestone, which should be replaced with the actual milestone value.  As an example, let's say you want to provide a link to where you can download your release, and the URL could be something like http://mydomain.com/releases/0.1.0.  You don't want to have to hard code the milestone number into your yaml configuration, so instead, you can use a replacement string in your footer-content, which will then be replaced with the actual milestone release number, when the release is created.  Default is false.
+* **milestone-replace-text**
+  * A string value which contains the string which should be replaced in the footer-content with the actual milestone release number. Default is an empty string.
 
 See the [example create configuration section](create-configuration) to see an example of how a footer can be configured.
 
 ## Export Options
 
-  * **include-created-date-in-title**
-    * A boolean value which indicates whether the date of which a Release occurred should be included within the heading section of generated release notes.  Default is false.
-  * **created-date-string-format**
-    * A string value which contains the Date Time Format string which should be used when including the created date in the title of the release notes.  Default is an empty string.
-  * **perform-regex-removal**
-    * A boolean value which inidcates whether a regular expression should be performed on the generated release notes to remove some text.  Default is false.
-  * **regex-text**
-    * A string value which contains the regular expression to match against the generated release notes, in order to remove text.  Default in an empty string.
-  * **multiline-regex**
-    * A boolean value which indicates that the regular expression should span multiple lines.  Default is false.
+* **include-created-date-in-title**
+  * A boolean value which indicates whether the date of which a Release occurred should be included within the heading section of generated release notes.  Default is false.
+* **created-date-string-format**
+  * A string value which contains the Date Time Format string which should be used when including the created date in the title of the release notes.  Default is an empty string.
+* **perform-regex-removal**
+  * A boolean value which inidcates whether a regular expression should be performed on the generated release notes to remove some text.  Default is false.
+* **regex-text**
+  * A string value which contains the regular expression to match against the generated release notes, in order to remove text.  Default in an empty string.
+* **multiline-regex**
+  * A boolean value which indicates that the regular expression should span multiple lines.  Default is false.
 
 See the [example export configuration section](export-configuration) to see an example of how the export can be configured.