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
|`GITHUB_TOKEN`| Your GitHub token for authentication. Store it as a secret and reference it in the workflow file as secrets.GITHUB_TOKEN. | Yes ||
46
-
|`tag-name`| The name of the tag for which you want to generate release notes. This should be the same as the tag name used in the release workflow. | Yes ||
47
-
|`from-tag-name`| The name of the tag from which you want to generate release notes. | No | '' |
48
-
|`chapters`| An YAML array defining chapters and corresponding labels for categorization. Each chapter should have a title and a label matching your GitHub issues and PRs. | Yes ||
49
-
|`row-format-issue`| The format of the row for the issue in the release notes. The format can contain placeholders for the issue `number`, `title`, and issues `pull-requests`. The placeholders are case-sensitive. | No |`"{number} _{title}_ in {pull-requests}"`|
50
-
|`row-format-pr`| The format of the row for the PR in the release notes. The format can contain placeholders for the PR `number`, and `title`. The placeholders are case-sensitive. | No |`"{number} _{title}_"`|
51
-
|`row-format-link-pr`| If defined `true`, the PR row will begin with a `"PR: "` string. Otherwise, no prefix will be added. | No | true |
52
-
|`duplicity-scope`| Set to `custom` to allow duplicity issue lines to be shown only in custom chapters. Options: `custom`, `service`, `both`, `none`. | No |`both`|
53
-
|`duplicity-icon`| The icon used to indicate duplicity issue lines in the release notes. Icon will be placed at the beginning of the line. | No |`🔔`|
54
-
|`published-at`| Set to true to enable the use of the `published-at` timestamp as the reference point for searching closed issues and PRs, instead of the `created-at` date of the latest release. If first release, repository creation date is used. | No | false |
55
-
|`skip-release-notes-labels`| List labels used for detection if issues or pull requests are ignored in the Release Notes generation process. Example: `skip-release-notes, question`. | No |`skip-release-notes`|
56
-
|`verbose`| Set to true to enable verbose logging for detailed output during the action's execution. | No | false |
57
-
|`release-notes-title`| The title of the release notes section in the PR description. | No |`[Rr]elease [Nn]otes:`|
58
-
|`coderabbit-support-active`| Enable CodeRabbit support. If true, the action will use CodeRabbit to generate release notes. | No | false |
59
-
|`coderabbit-release-notes-title`| The title of the CodeRabbit summary in the PR body. Value supports regex. | No |`Summary by CodeRabbit`|
60
-
|`coderabbit-summary-ignore-groups`| List of "group names" to be ignored by release notes detection logic. Example: `Documentation, Tests, Chores, Bug Fixes`. | No | '' |
|`GITHUB_TOKEN`| Your GitHub token for authentication. Store it as a secret and reference it in the workflow file as secrets.GITHUB_TOKEN. | Yes ||
48
+
|`tag-name`| The name of the tag for which you want to generate release notes. This should be the same as the tag name used in the release workflow. | Yes ||
49
+
|`from-tag-name`| The name of the tag from which you want to generate release notes. | No | '' |
50
+
|`chapters`| An YAML array defining chapters and corresponding labels for categorization. Each chapter should have a title and a label matching your GitHub issues and PRs. | Yes ||
51
+
|`regime`| Controls the regime of the action. Options: `default`. See more about the [Regimes](#regimes). | No |`default`|
52
+
|`row-format-issue`| The format of the row for the issue in the release notes. The format can contain placeholders for the issue `number`, `title`, and issues `pull-requests`. The placeholders are case-sensitive. | No |`"{number} _{title}_ in {pull-requests}"`|
53
+
|`row-format-pr`| The format of the row for the PR in the release notes. The format can contain placeholders for the PR `number`, and `title`. The placeholders are case-sensitive. | No |`"{number} _{title}_"`|
54
+
|`row-format-link-pr`| If defined `true`, the PR row will begin with a `"PR: "` string. Otherwise, no prefix will be added. | No | true |
55
+
|`duplicity-scope`| Set to `custom` to allow duplicity issue lines to be shown only in custom chapters. Options: `custom`, `service`, `both`, `none`. | No |`both`|
56
+
|`duplicity-icon`| The icon used to indicate duplicity issue lines in the release notes. Icon will be placed at the beginning of the line. | No |`🔔`|
57
+
|`published-at`| Set to true to enable the use of the `published-at` timestamp as the reference point for searching closed issues and PRs, instead of the `created-at` date of the latest release. If first release, repository creation date is used. | No | false |
58
+
|`skip-release-notes-labels`| List labels used for detection if issues or pull requests are ignored in the Release Notes generation process. Example: `skip-release-notes, question`. | No |`skip-release-notes`|
59
+
|`verbose`| Set to true to enable verbose logging for detailed output during the action's execution. | No | false |
60
+
|`release-notes-title`| The title of the release notes section in the PR description. | No |`[Rr]elease [Nn]otes:`|
61
+
|`coderabbit-support-active`| Enable CodeRabbit support. If true, the action will use CodeRabbit to generate release notes. | No | false |
62
+
|`coderabbit-release-notes-title`| The title of the CodeRabbit summary in the PR body. Value supports regex. | No |`Summary by CodeRabbit`|
63
+
|`coderabbit-summary-ignore-groups`| List of "group names" to be ignored by release notes detection logic. Example: `Documentation, Tests, Chores, Bug Fixes`. | No | '' |
61
64
62
65
> **Notes**
63
66
> -`skip-release-notes-labels`
@@ -78,6 +81,20 @@ Generate Release Notes action is dedicated to enhance the quality and organizati
78
81
> -`warnings`
79
82
> -**Disabling this feature will hide service chapter showing direct commits!** These cannot be visible in custom chapters as they do not have labels!
80
83
84
+
### Regimes
85
+
86
+
### Default regime
87
+
88
+
The basic regime for this action.
89
+
90
+
-**Data management**
91
+
- The issue type is not used. It can lead to placing Epic and other issues without linked PR into service chapters. If you need to use issue type use another regime.
92
+
-**Release notes**
93
+
- Organized by custom chapters defined by user using labels.
94
+
- Used these `types of rows`:
95
+
- Issue with/without linked Pull Request(s).
96
+
- Pull Request without linked Issue.
97
+
- Direct commits (without Issue and Pull Request).
81
98
82
99
## Outputs
83
100
The output of the action is a markdown string containing the release notes for the specified tag. This string can be used in subsequent steps to publish the release notes to a file, create a GitHub release, or send notifications.
0 commit comments