[Bug] Bump commits ALL files

Description

Instead of committing just all files containing a version ALL changed files are committed (new ones are not just changed ones). This is not good if a change is not meant to be included in the release.

While this can be avoided by branching it should still behave different as git add . and git commit <whatever> is very carelessly.

Steps to reproduce

1. Create repo and add cz config file
2. Add file1.txt and file2.txt
3. stage and Commit file1
4. cz bump (Behaves as expected)
5. Commit the adding of file2
6. Change the content of file1 and don’t stage it
7. cz bump

You will see that all changes of file1 are commited in the bump: 0.0.1 -> 0.0.2 commit

Desired behavior

When executing a cz bump

1. Stash the changes and added files (staged and unstaged the same)
2. Warn the user if he has Staged files because they will be merged with the unstaged ones when stashing
3. Execute the bump
4. Pop the stash
5. Delete the stash

Environment

• commitizen version:2.13.0

• python version:Python 2.7.17

• operating system:Linux

[woile]

I’m in as a positional argument as well. I’d like to see an implementation 👍🏻

[Lee-W]

The “auto stashing” option sounds good to me as long as we do not set it as the default behavior. If we’d like to do so in the future, we’ll need to bump a major version