(#568) Set the 'Due date' when closing a milestone if configured to do so #614
+19
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Resolves #568 |
This is controlled via new set-due-date value in the close section of the GitReleaseManager.yaml file. This operation is disabled by default, and something which the user has to opt into to make use of.
gep13
changed the title
|
@Jericho thank you very much for getting this PR put up! I have just taken this for a spin, both against GitHub and GitLab, and I am happy to say that this is working as expected! Going to go ahead and get this merged in, once the CI builds complete. We will need to update the documentation to include this new configuration option, but I will try to take care of that later today. |
|
@Jericho I have updated the documentation to include this new option in the configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow developers to set a Boolean setting indicating whether they want the due date to be set when a milestone is closed.
By default, this config setting is set to "false" to preserve the current behavior.