To start, I really love your package. It is super handy and helps a lot to automate the versioning.

The way ccount works currently, it has basically two functions. Either it counts the commits since the last edit of the VERSION file, or it counts the commits since the last Git tag in the git repository graph.

This can introduce an issue into the versioning. Assume we have a feature branch originating from dev. We start to work on it and do some commits. At some point, we set a new tag on the dev branch. If our feature branch originated from the commit of dev, on which we set the tag. This will reset the ccount and possibly give us duplicated version numbers on the feature branch discussed before.

Let me try to visualize this with the following graphs.

If instead of the ccount, I could use the version_ccount (which only counts the commits since the last changes in the VERSION file), I could prevent the counter from accidentally being reset if someone adds a tag in Git.

I hope this helps to clarify my issue. Please let me know if you need any further information.