Merge pull request #215 from arturcic/feature/GH-214

Add option to allow updating published release

Author: gep13

Source/GitReleaseManager/Configuration/Config.cs

@@ -32,6 +32,7 @@ public Config()
                 IncludeShaSection = false,
                 ShaSectionHeading = "SHA256 Hashes of the release artifacts",
                 ShaSectionLineFormat = "- `{1}\t{0}`",
+                AllowUpdateToPublishedRelease = false,
             };
 
             Export = new ExportConfig

Source/GitReleaseManager/Configuration/CreateConfig.cs

@@ -38,5 +38,8 @@ public class CreateConfig
 
         [YamlMember(Alias = "sha-section-line-format")]
         public string ShaSectionLineFormat { get; set; }
+
+        [YamlMember(Alias = "allow-update-to-published")]
+        public bool AllowUpdateToPublishedRelease { get; set; }
     }
 }

Source/GitReleaseManager/GitHubProvider.cs

@@ -153,7 +153,7 @@ public async Task<Release> CreateReleaseFromMilestone(string owner, string repos
             {
                 _logger.Warning("A release for milestone {Milestone} already exists, and will be updated", milestone);
 
-                if (!release.Draft)
+                if (!release.Draft && !_configuration.Create.AllowUpdateToPublishedRelease)
                 {
                     throw new InvalidOperationException("Release is not in draft state, so not updating.");
                 }

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

@@ -20,6 +20,7 @@ create:
     include-sha-section: false
     sha-section-heading: "SHA256 Hashes of the release artifacts"
     sha-section-line-format: "- `{1}\t{0}`"
+    allow-update-to-published: false
 export:
     include-created-date-in-title: false
     created-date-string-format: ''
@@ -103,6 +104,10 @@ control the look and feel of the generated release notes.
         used when creating the SHA256 hash entries in the release notes.
         Default is ``- `{1}\t{0}` `` **NOTE:** This configuration option was added
         in version 0.9.0 of GitReleaseManager.
+- **allow-update-to-published**
+  - A boolean value which indicates whether or not updates can be applied to
+        published releases. The default value is false. **NOTE:** This
+        configuration option was added in version 0.11.0 of GitReleaseManager.
 
 See the [example create configuration section](create-configuration) to see an
 example of how a footer can be configured.