Autolabel versions about cutsolver HOT 8 CLOSED

https://pre-commit.com/ works as entry point

https://gitpython.readthedocs.io/en/stable/ is used to modify tags

from cutsolver.

can't tag in pre-commit, need post-commit at the earliest. Still can't really change python code from cli without risking integrity. -> python to git needed instead

from cutsolver.

won't work. Commit needs to exist to be tagged, pre-push is too late as it won't allow "staging" the tag as well. post-commit needed, see pre-commit/pre-commit#1411

from cutsolver.

Oh, btw, pycharm push won't respect pipenv shell, see pre-commit/pre-commit#1412

from cutsolver.

Use a common source for both versions instead?

1. version as text file, read by app on startup
2. fetch version file in github repo by running app to check internal version (would need requests or something similar, see #37 for some references)
3. write script that increases version in file and tags git commit

from cutsolver.

Git hook reference: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

from cutsolver.

GitPython could push the new tag by itself, but pushing inside a push hook sounds like a really stupid idea, especially since the inner push tag refers to an outer push commit.

from cutsolver.

https://youtrack.jetbrains.com/issue/PY-12988 should make these prefixes obsolete

from cutsolver.