If I tag commits that I am working on, then push changes to another repo, I understand that I can also be pushing tag objects. Can I create tags that are not pushed? Are e.g. lightweight tags never pushed, but tag objects always are?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I tag commits that I am working on, then push changes to another repo, I understand that I can also be pushing tag objects. Can I create tags that are not pushed? Are e.g. lightweight tags never pushed, but tag objects always are?
Tags are created in
.git/refs/tags/and anything under.git/refscan potentially be pushed, based on the flags that you add to push or other commands. With that said,http://progit.org/book/ch2-6.html
As per @Vincent Scheib’s comment asking about the below quoted comment in another question:
“if you create new commits on your branch, and then push (so there is something to transfer), git should detect all new tags that point to commits that are present after push on remote side, and push them too.”
It is not valid. It is applicable when fetching though, but wrongly thought to be applicable for push.