Skip to content

Commit 4b545bd

Browse files
committed
(doc) Document the new set-due-date option
1 parent 091523b commit 4b545bd

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

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

+7
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ export:
2929
multiline-regex: false
3030
close:
3131
use-issue-comments: false
32+
set-due-date: false
3233
issue-comment: |-
3334
:tada: This issue has been resolved in version {milestone} :tada:
3435
@@ -186,6 +187,12 @@ tokenized values, such as milestone, owner, repository, with the actual values.
186187
- This is a template for what comment should be added to each issue. Within
187188
this comment template, it is possible to replace information for example,
188189
the milestone name, the owner/repository information, etc.
190+
- **set-due-date**
191+
- A boolean value which indicates whether or not to set the due date of the
192+
milestone when closing it. The date which it is set to, is the same as the
193+
date at which the command was run, it is not possible to provide a
194+
different date. **NOTE:** This configuration option was added in version
195+
0.19.0 of GitReleaseManager.
189196

190197
## Default branch
191198

0 commit comments

Comments
 (0)