I have commitizen-tools/commitizen-action@0.21.0 in my workflow running cz bump, but as I've been working on getting it set up properly, I've run into an issue where if it fails and I need to re-run the workflow it's guaranteed to fail on retry because cz bump fails if the target tag already exists.
Commitizen version: 3.30.0
cz --no-raise 21 bump --yes --changelog --check-consistency
bump: version 0.3.0 → 0.4.0
tag to create: 0.4.0
increment detected: MINOR
[main 216[83](https://github.com/ascend-io/gitops-glue/actions/runs/11524448035/job/32084730449#step:6:84)1d] bump: version 0.3.0 → 0.4.0
2 files changed, 7 insertions(+), 1 deletion(-)
fatal: tag '0.4.0' already exists
I would like for an option to just continue if the target tag already exists. I'm looking at ignoring raise on exit code 7 for BumpTagFailedError, but I suspect that includes failure scenarios that I would not want to ignore where the tag bump really just failed.
I have
commitizen-tools/commitizen-action@0.21.0in my workflow running cz bump, but as I've been working on getting it set up properly, I've run into an issue where if it fails and I need to re-run the workflow it's guaranteed to fail on retry becausecz bumpfails if the target tag already exists.I would like for an option to just
continueif the target tag already exists. I'm looking at ignoring raise on exit code 7 forBumpTagFailedError, but I suspect that includes failure scenarios that I would not want to ignore where the tag bump really just failed.