-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Git push does not transfer tags #3740
Comments
Good idea. A pull request documenting this would be merged for sure! 👍🏼 |
Sure, I've got a PR ready. Do I fork the repo or do you grant access to creating branches in this repo or how is the preferred contribution style here? (...which I might as well add to CONTRIBUTING.md while I'm at it) |
Please create a fork and create the PR |
Well the PR doesn't build I can confirm, independently of the testing workflow, that the link causing the build failure does not work. It is a link in a different part of the documentation, located at: https://gitversion.net/docs/learn/branching-strategies/githubflow/ that has nothing to do with this change. Still, it might be better to do something about the issue. Are there any policies on removing links? |
🎉 This issue has been resolved in version 6.0.0-beta.4 🎉 Your GitReleaseManager bot 📦🚀 |
NB: This is not a problem with gitversion-the-software, but it sure did take me long to find out why gitversion wasn't updating.
Starting this off: Gitversion gave different numbers locally and in my github job.
Reading the FAQ:
Well, then I clicked the link and on that page I saw:
And I knew that I had God damn well tagged my commits.
So I went to the issue tracker and, yeah, there were issues about tags not being tracked - closed issues, by people who had resolved their problems, so ... probably not an issue with gitversion-the-software?
And then I read up on git tags (which I have never used before getting into gitversion) and found out that git push does not transfer tags, which explains the whole thing.
But it would have been nice to read that in the FAQ on gitversion. It happened to me - it could happen to others.
The text was updated successfully, but these errors were encountered: