Our project recently moved from Sourceforge to GitHub. The migration did not include the subversion tags. I have very little Git skill, so I used 2.6 Git Basics - Tagging as a guide.I performed a Git checkout:$ git clone https://github.com/weidai11/cryptopp.git cryptopp-gitI then went through and reproduced the tags for the last 15 years or so using:# Produce a log file$ git log --all --oneline > git.log# Look for the subversion commit (yes; it was a CVS migration 15 or so years ago):$ awk 'NR==(872-3)' git.log bf7ae38 This commit was manufactured by cvs2svn to create tag 'CRYPTOPP_5_0'.# Tag it:$ git tag -a CRYPTOPP_5_0 bf7ae38[Add message in emacs]# Lather, rinse, repeat...Next, I tried to commit them:$ git commit -m Rebuild tags after GitHub importOn branch masterYour branch is up-to-date with 'origin/master'.nothing to commit, working directory clean$ git pushEverything up-to-dateSo I went to another machine to verify the work. I performed a git pull (Debian 8 Chroot on a distinct machine):# git pullAlready up-to-date.# git show CRYPTOPP_5_0fatal: ambiguous argument 'CRYPTOPP_5_0': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git <command> [<revision>...] -- [<file>...]'The best I can tell, the information has not been checked-in to GitHub.How, exactly, do I check-in the tags to GitHub?
How to check-in annotated tags?
git;github;tagging
You have to use the --tags option of git push. This will push your tags to the remote.git push --tagsNote that this is not a feature of GitHub, but normal git behaviour. Also have a look at the git push man page.