You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you likely know you can tag old commits, too, and you can even have the correct date for them like git tag -a v1.2 9fceb02 -m "Message here" and the more in-depth answer on How to tag an older commit in Git? that notes how to tag with the correct date.
And of course: please tag new versions (in an ideal world you can use CI to publish to all market places / vsix registries you like to, by just committing a tag that matches with v[:number:]\.[:number:]\.[:number:].
The text was updated successfully, but these errors were encountered:
If you agree I'd like to inspect the old versions and post-tag those, too.
I'd then add a script here to create the tags which can then be pushed to GH (I think I won't be able to push those but could try that, too).
What do you think? If you are fine with this: just reopen and assign it to me and I'll check for the necessary commands and commit hashes for the versions.
As you likely know you can tag old commits, too, and you can even have the correct date for them like
git tag -a v1.2 9fceb02 -m "Message here"
and the more in-depth answer on How to tag an older commit in Git? that notes how to tag with the correct date.And of course: please tag new versions (in an ideal world you can use CI to publish to all market places / vsix registries you like to, by just committing a tag that matches with
v[:number:]\.[:number:]\.[:number:]
.The text was updated successfully, but these errors were encountered: