Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[skip-ci] generates an invalid commit message #999

Open
tkschmidt opened this issue Sep 20, 2024 · 1 comment
Open

[skip-ci] generates an invalid commit message #999

tkschmidt opened this issue Sep 20, 2024 · 1 comment

Comments

@tkschmidt
Copy link

Hey *,
I've prepared an internal repository to enable the provided gitlab-ci template. The manual states that The commit message executed automatically by the CI must include [skip-ci]

I have done so via the provided example.

So my .cz.toml looks like

[tool.commitizen]
name = "cz_conventional_commits"
tag_format = "$version"
version_scheme = "semver"
version_provider = "cargo"
update_changelog_on_bump = true
major_version_zero = true
bump_message = "release $current_version → $new_version [skip-ci]"

If I run now locally (or within the CI) cz bump, it shows me the following error message:

release 0.5.0 → 0.6.0 [skip-ci]
tag to create: 0.6.0
increment detected: MINOR

2nd git.commit error: "commitizen check.........................................................Failed
- hook id: commitizen
- exit code: 14

commit validation: failed!
please enter a commit message in the commitizen format.
commit "": "release 0.5.0 → 0.6.0 [skip-ci]"
pattern: (?s)(build|ci|docs|feat|fix|perf|refactor|style|test|chore|revert|bump)(\(\S+\))?!?:( [^\n\r]+)((\n\n.*)|(\s*))?$"

What am I doing wrong?

Best,
Tobi

@revelt
Copy link
Contributor

revelt commented Feb 28, 2025

The colon after release in bump_message was missing, validation failed because of that.

@tkschmidt if it's resolved, please close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants