@@ -9,8 +9,8 @@ Docker image: [stepin/git-parse-commits:latest](https://hub.docker.com/r/stepin/
9
9
Example how to use with Docker:
10
10
11
11
``` shell
12
- docker run --rm -it -v " $( PWD) :/git" -w /git --user " $( id -u) " stepin/git-parse-commits:1 .0.2 releaseVersion
13
- docker run --rm -it -v " $( PWD) :/git" -w /git --user " $( id -u) " stepin/git-parse-commits:1 .0.2 releaseNotes
12
+ docker run --rm -it -v " $( PWD) :/git" -w /git --user " $( id -u) " stepin/git-parse-commits:2 .0.0 releaseVersion
13
+ docker run --rm -it -v " $( PWD) :/git" -w /git --user " $( id -u) " stepin/git-parse-commits:2 .0.0 releaseNotes
14
14
```
15
15
16
16
Example usage for Gitlab:
@@ -19,7 +19,7 @@ Example usage for Gitlab:
19
19
create_changelog :
20
20
stage : " build"
21
21
image :
22
- name : " stepin/git-parse-commits:1 .0.2 "
22
+ name : " stepin/git-parse-commits:2 .0.0 "
23
23
entrypoint : [""]
24
24
variables :
25
25
GIT_DEPTH : " 0"
@@ -75,31 +75,25 @@ release:
75
75
` ` `
76
76
docker run --rm -it stepin/git-parse-commits --help
77
77
78
- usage : git-parse-commits [-h] [-j] [-t [TAG_PREFIX]] [-s [SCOPE]] [-i [INITIAL_REVISION]] [-l [LAST_REVISION]] [--tag]
79
- {version,currentVersion,lastReleaseVersion,releaseVersion,releaseNotes} ...
80
-
81
- Provides next release version and release notes from git commit messages.
82
-
83
- positional arguments :
84
- {version,currentVersion,lastReleaseVersion,releaseVersion,releaseNotes}
85
- version Prints version of this tool
86
- currentVersion Prints current version (useful for non-release builds)
87
- lastReleaseVersion Prints version of last release
88
- releaseVersion Prints version of next release from git commit messages
89
- releaseNotes Prints release notes from git commit messages
90
-
91
- options :
92
- -h, --help show this help message and exit
93
- -j, --json Output in json format
94
- -t [TAG_PREFIX], --tag-prefix [TAG_PREFIX]
95
- prefix for tags (optional)
96
- -s [SCOPE], --scope [SCOPE]
97
- scope to filter release note items
98
- -i [INITIAL_REVISION], --initial-revision [INITIAL_REVISION]
99
- start range from next revision
100
- -l [LAST_REVISION], --last-revision [LAST_REVISION]
101
- stop on this revision
102
- --tag add tag prefix to version (only if tag prefix is defined)
78
+ Usage : git-parse-commits [<options>] <command> [<args>]...
79
+
80
+ Provides next release version and release notes from git commit messages.
81
+
82
+ Options :
83
+ -j, --json output in json format
84
+ -t, --tag-prefix=<text> prefix for tags (optional)
85
+ --tag add tag prefix to versions (only if tag prefix is defined)
86
+ -s, --scope=<text> scope to filter release note items
87
+ -i, --initial-revision=<text> start range from next revision
88
+ -l, --last-revision=<text> stop on this revision
89
+ -h, --help Show this message and exit
90
+
91
+ Commands :
92
+ version Prints version of this tool
93
+ currentVersion Prints current version (useful for non-release builds)
94
+ lastReleaseVersion Prints version of last release
95
+ releaseVersion Prints version of next release from git commit messages
96
+ releaseNotes Prints release notes from git commit messages
103
97
` ` `
104
98
105
99
@@ -240,13 +234,17 @@ Feel free to send MRs/patches.
240
234
241
235
Following components should be installed locally (or in Docker):
242
236
243
- - Python 3
237
+ - Kotlin
244
238
- git
245
239
- bash
246
240
- jq https://jqlang.github.io/jq/
247
241
- jc https://github.com/kellyjonbrazil/jc
248
242
249
243
``` bash
250
- brew install jq jc
251
- poetry install
244
+ brew install jq jc kotlin
252
245
```
246
+
247
+ Currently, it's not possible to split single script to several files. So, it will be when it will
248
+ be possible (like around Kotlin 2.0.20).
249
+
250
+ Also, it's not clear how to write unit tests for this script. Ping me if you know some example / article.
0 commit comments