Closed tnjordan closed 1 year ago
Thanks for reporting @tnjordan! I found out about this issue today as well.
I've confirmed that this is a bug. Fix is coming here https://github.com/iterative/gto/pull/417 . Sorry for the inconvenience folks. There was a lack of tests that made the last refactoring fragile a bit.
Should be fixed in the 1.3.0 that should be published today.
The gto command has a --push flag which according to the docs will push a created tag.
--push - Push created tag automatically (experimental)
However, looking into the code the tag will automatically be pushed if the git repository has a remote.
This is unexpected as it is not a mentioned actions in the docs. I looked back into a older versions of gto (v0.3.5) and saw that there was similar logic, but found the logic to not be implemented/functional.
I have a github action that automatically increments the tag version when changes are pushed to a branch (prod).
This action was working with gto prior to the version 1 release. It now fails with the logs:
I am not sure why the automatic gto register push is failing; however, I would suggest that the push only happens when the
--push
flag is provided. An additional--auto-push
flag could be created that could cover the current behavior.Alternatively pushing could be the default behavior and a
--no-push
flag could be provided to prevent pushing.