JIYIK CN >

If you create a git tag locally, your intention must be to share your changes with your team for easy tracking.

Commit is one of the common operations to share changes. But another sharing and tracking idea added to it is Git Tags.

This article will introduce how to push the created Git Tag to the remote repository and the best practices.

Push Git tags to remote repositories

Use the following code to push the tag to your remote repository.

git push <remote> <tagname>

Here is an example:

git push origin v1

Push all Git tags

Use the following code to push all tags to your remote repository.

git push <remote> --tags

Here is an example.

git push origin --tags

WARNING: Removing tags can be very difficult. So we don't recommend you use or train people to push all tags, including bad and unannotated tags!

For team purposes, poorly named labels can be confusing and can make your collaboration as confusing as possible.

Creating a Git Tag

There are two kinds of git tags - Annotated and Lightweight.

To create an annotated git tag, use the following code.

git tag <tag_name> -a -m "Message"

Here is an example:

git tag v1 -a -m "Message"

To create a lightweight git tag, use the following code.

git tag <tag_name>

Here is an example.

git tag v1

To create a lightweight git tag with a description, use the following code.

git tag <tag_name> -a

Here is an example:

git tag v1 -a

Check out the newly created Git tag

git show <tag-name>

The difference between annotated tags and lightweight tags is that the annotated word itself indicates that the tag is annotated with a message, while lightweight tags do not retain such information.

in conclusion

According to best practices, based on experience, developers realized that pushing all tags at once is a bad practice.

Always check with your team leader about how your collaboration works. Does your team use tags? Do you need them to track your changes? What tag names or conventions does your team agree to stick to?

It is encouraged, especially for large projects, to use not only commit messages but also tags.

Okay, think about this, let's say you have a project that is 70% done right now, think of any changes you want to review and look back at. I imagine you're going to be miserable using the commit log and looking at the full list of commits that you and your teammates have 50% of. But what if you have tags? Then that's very helpful!