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
Want to automate the process of updating your Changelog withs GitHub Actions? Checkout the [stefanzweifel/changelog-updater-action](https://github.com/stefanzweifel/changelog-updater-action) which does exactly that.
12
+
Want to automate the process of updating your Changelog with GitHub Actions? Checkout the [stefanzweifel/changelog-updater-action](https://github.com/stefanzweifel/changelog-updater-action) which does exactly that.
13
13
14
14
## Installation
15
15
@@ -52,7 +52,7 @@ The CLI also looks for a second level heading with the name of the previous vers
52
52
Here is an example Markdown file, that will work fine with the CLI.
53
53
54
54
55
-
```md
55
+
```
56
56
# Changelog
57
57
All notable changes to this project will be documented in this file.
58
58
@@ -69,15 +69,15 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
69
69
- Initial Release
70
70
```
71
71
72
-
The content between the "Unreleased"-heading the the latest version will remain untouched by the CLI.
72
+
The content between the "Unreleased"-heading and the latest version will remain untouched by the CLI.
73
73
74
74
### CLI Options
75
75
76
76
### `--release-notes`
77
77
**Required**. The release notes you want to add to your CHANGELOG. Should be markdown.
78
78
79
79
### `--latest-version`
80
-
**Required**. Semantic version number of the latest release. The value will be used as the heading text and as a parameter in the compare URL.
80
+
**Required**. Version number of the latest release. The value will be used as the heading text and as a parameter in the compare URL.
0 commit comments