Git tags dissapear when doing a push then clone?

We have a repository with multiple tags. Each tag represents a version of the software. We are pushing the repository to a remote server.

When we do a fresh clone off the remote server, the tags are no longer there. How do you ensure other developers or clients can check out specific versions of software off the remote server?

  • changing the last commit message without committing newest changes
  • GIT: I want to unstage all files matching a certain pattern
  • Jenkins and only build feature branches?
  • Alternatives to GitHub Pages?
  • Git merge changes between two specific commits from another branch
  • git checkout error: unable to create file
  • How to copy a local Git branch to a remote repo
  • Git notes details
  • Specific git branches for aws elastic beanstalk environments
  • Use another partition for temporary git operations (git gc)
  • TortoiseGit icons overlays icons on desktop
  • Is it possible to trigger a dependent build only in case the first in the chain is built from default branch?
  • 3 Solutions collect form web for “Git tags dissapear when doing a push then clone?”

    git push --tags or git push remote tag-name

    Alternate solution to the one given by Brian Campbell would be to configure remote to push all refs, or push all branches and tags:

    [remote "repository"]
            url = user@example.com:user/repo.git
            push  = +refs/heads/*:refs/heads/*
            push  = +refs/tags/*:refs/tags/*
    

    Note that, since git 1.8.3 (April 22d, 2013), a:

    git push --follow-tags
    

    would push any new commits as well as all annotated tags referenced by pushed commits.

    Git Baby is a git and github fan, let's start git clone.