You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/options.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,18 +16,20 @@ To pass it to the `GithubReleaseNotes` class, in the [configuration file](#confi
16
16
17
17
| Command | Options | Description | Default |
18
18
| ------- | ------- | ----------- | ------- |
19
-
|`api-url`|**Optional**| Override the GitHub API URL, allows **gren** to connect to a private [GHE](https://enterprise.github.com/) installation. _e.g. `https://my-enterprise-domain.com/api/v3`_|`null`|
20
19
|`username`|**Required**| The username of the repo _e.g. `github-tools`_|`null`|
21
20
|`repo`|**Required**| The repository name _e.g. `github-release-notes`_|`null`|
21
+
|`api-url`|**Optional**| Override the GitHub API URL, allows **gren** to connect to a private [GHE](https://enterprise.github.com/) installation. _e.g. `https://my-enterprise-domain.com/api/v3`_|`null`|
22
22
|`action`|`release``changelog`| The **gren** action to run. _(see details below for changelog generator)_|`release`|
23
23
|`tags`|`0.1.0``0.2.0,0.1.0``all`| A specific tag or the range of tags to build the release notes from. You can also specify `all` to write all releases. _(To override existing releases use the --override flag)_|`false`|
24
24
|`ignore-labels`|`wont_fix``wont_fix,duplicate`| Ignore the specified labels. |`false`|
25
25
|`ignore-issues-with`|`wont_fix``wont_fix,duplicate`| Ignore issues that contains one of the specified labels. |`false`|
26
-
|`data-source`|`issues``commits`| The informations you want to use to build release notes. |`issues`|
26
+
|`data-source`|`issues``commits``milestones`| The informations you want to use to build release notes. For more informations about the `milestones` option, [have a look here]({{ "example#milestones" | relative_url }}) |`issues`|
27
+
|`milestone-match`|**String**| The title that the script needs to match to link the release to the milestone. [See further details]({{ "example#milestones" | relative_url }}) |`null`|
27
28
|`prefix`|**String**`e.g. v`| Add a prefix to the tag version. |`null`|
28
29
|`override`|**Flag**| Override the release notes if existing. |`false`|
29
30
|`include-messages`|`merge``commits``all`| Filter the messages added to the release notes. _Only used when `data-source` used is `commits`|`commits`|
30
31
|`group-by`|`label``{...}`| Group the issues using the labels as group headings. You can set custom headings for groups of labels. [See example]({{ "example#group-by" | relative_url }}) |`false`|
32
+
|`only-milestones`|**Flag**| Add to the release bodies only the issues that have a milestone |`false`|
0 commit comments