Versionize fails with repository dirty with untracked files present while git reports repo is not dirty

[jmartens]

Versionize fails when there are files that are not tracked in the folder of the repository mentioning the repository is dirty. Git does not describe this as dirty as it is perfectly fine to have untracked files in the same folder.

I would not have expected this to be preventing versionize to run and if it was a problem I would have expected a message stating that there are untracked files, not the repo being dirty since git's dirty has a different meaning.

[saintedlama]

Investigating that use case currently, it's feasible to be fixed but might lead to some unintended behavior. Before digging deeper, what's the use case for excluding the untracked files from git status check to determine if a repo is dirty?

[cn-ml]

It would be nice to see which files are not clean (i.e. prevent the tool from running). I just tried to configure my CI with versionize and failed because of this error. Currently i am running a git reset --hard at the start of my ci script to clean the environment.

[smitchamwork]

As a debug step I added a 'git diff' into my build script on the line prior to versionize, however, something built in would be nice. In my case it was script files that weren't set as executable in the index that were automatically getting converted by Github actions to executable.