I think I see the side effect of this. Now the pipelines throw an error when no change is found.
But I guess is an edge we have to properly polish

yep, after a second thought, this could be a problem. but i've not yet get a better idea

look like we'll need to handle it on our side as well 🤔
maybe we'll need to add documentation for it?
https://github.com/commitizen-tools/commitizen/runs/4960945320?check_suite_focus=true

I'm starting to think that I made a mistake here by using the same error code.

On one hand you have new commits that you expect to be ignored (those commits starting with things like docs, ci, etc).
And on the other hand, you have the "no commits" situation, where the pipeline is triggered and there's no new commits (this is probably because of a bad CI design, like triggering the pipeline when a new PR is made).

Maybe we can change the error code for this and introduce a new flag: --no-raise with error codes.
It would terminate the program but with error code 0.
Example:

cz bump --no-raise 3,5,8

That would make it quite flexible, no?

Yep! Sounds like a great solution! I was using $? in Makefile to decide whether I should ignore the error on other projects. Wondering if --no-raise is used in other project 🤔 Also, I think it might be great if we could support string input as well.

e.g.,

cz [any operation] --no-raise NO_COMMITS,NO_BUMP

or should we go with

cz [any operation] --no-raise NO_COMIITS --no-raise NO_BUMP

I have no strong preference between these 2. Or we could support both? 🤔

I just create an issue for this #485. let's discuss there 💪