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
check consistency among versions defined in commitizen
84
84
configuration and version_files
85
-
--annotated-tag, -at create annotated tag instead of lightweight one
86
-
--signed-tag, -st create a signed tag instead of lightweight one or annotated tag
85
+
--annotate, -a create annotated tag instead of lightweight one
86
+
--sign, -s create a signed tag instead of lightweight one or annotated tag
87
87
--changelog-to-stdout
88
88
Output changelog to the stdout
89
89
--retry retry commit if it fails the 1st time
@@ -163,9 +163,9 @@ version = "5.3.5+0.1.0"
163
163
164
164
If `--local-version` is used, it will bump only the local version `0.1.0` and keep the public version `5.3.5` intact, bumping to the version `5.3.5+0.2.0`.
165
165
166
-
### `--annotated-tag`
166
+
### `--annotate`
167
167
168
-
If `--annotated-tag` is used, commitizen will create annotated tags. Also available via configuration, in `pyproject.toml` or `.cz.toml`.
168
+
If `--annotate` is used, commitizen will create annotated tags. Also available via configuration, in `pyproject.toml` or `.cz.toml`.
| `version_files` | `list` | `[ ]` | Files were the version will be updated. A pattern to match a line, can also be specified, separated by `:` [See more][version_files] |
130
130
| `tag_format` | `str` | `None` | Format for the git tag, useful for old projects, that use a convention like `"v1.2.1"`. [See more][tag_format] |
0 commit comments