-
| Hi, We are tagging our repo in the following manner: Locally, when the gitversion commandline tool is used, we will see a SemVer like this, which is good and expected: However, we use GitHub actions to automate deployment of the software on pushing that tag. When run on the GitHub actions build server, the SemVer that GitVersion generates looks like this: With the version number (1.57.0) doubled, the literal word "tags", and a ".1" added to the end. We're not using a GitVersion.yml config, but just relying on the defaults. Thanks! | 
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
| Please see related issues: 
 I think we have a common deficit here. I invite you to help. | 
Beta Was this translation helpful? Give feedback.
-
| Indeed it is the same issue. I appreciate the quick response. It turns out that searching for "-tags" is quite difficult! | 
Beta Was this translation helpful? Give feedback.
Please see related issues:
I think we have a common deficit here. I invite you to help.