How do you create a Git tag?

Creating a Git tag is a way to label a specific commit in your Git history with a meaningful version number or other identifier. Tags are often used to mark releases or significant points in the project.

Git tags are like bookmarks, marking significant moments in your repository history. So, how do we create these markers? Step 1: Take a look at your commit history using git log. Copy the commit hash. Step 2: Run git tag -a <tag_name> <commit_hash>. Replace <tag_name> with your desired tag name and <commit_hash> with the copied commit hash. Step 3: After hitting enter, Git will prompt you to write a message. Once done, save and exit. Step 4: Push your tag to the remote repository using git push origin <tag_name>. Replace <tag_name> with the tag name you just created. Step 5: At this point you are done. Your tag is now easily accessible inside your repo. Happy coding and tagging!

On utilise généralement une branche "develop" pour pousser toutes les dernières modifications (depuis des MR). Créer un TAG permet de figer l'application à un instant T. Ainsi, les développeurs peuvent continuer à effectuer des modifications, vous pourrez déployer la version TAG de votre application, voir revenir en arrière en déployant un TAG précédent. Par exemple, une bonne pratique consiste à les nommer les TAG sous la forme : x.y.zRCn Où x est la version majeur, y la version mineur, z la modification de la version x.y. RC pour Release Candidate, n étant la version de cette RC. Et pour une version poussée en Prod, retirer RCn.

A tag in Git is a way of marking a specific point in the repository's history, typically used to denote release versions. Unlike branches, tags, once created, do not change; they are meant to point to specific commits.

El comando Git tag llega a ser de suma importancia para poder llevar un control sobre una versión estable y certificada, en cierta vida de ciclo del proyecto. Este punto creado por el tag podría ser un punto de rollback a su vez en caso de un posible error no controlado.

Keep in mind that tags cannot contain special characters or spaces. Also tags are not case sensitive. Just like branch names, follow a standard way to tag your releases.

Here's how you can create a Git tag: 1. Creating a Lightweight Tag: A lightweight tag is simply a reference to a specific commit. # Create a lightweight tag git tag <tag_name> # Example: git tag v1.0.0 2. Creating an Annotated Tag: An annotated tag is more detailed and includes a message, similar to a commit message. # Create an annotated tag git tag -a <tag_name> -m "Tagging version 1.0.0" # Example: git tag -a v1.0.0 -m "Tagging version 1.0.0" 3. Tagging a Specific Commit # Tag a specific commit git tag -a <tag_name> <commit_hash> # Example: git tag -a v1.0.0 abc1234

Listing and showing Git tags is a neat way to keep track of important milestones in your project. Think of it like flipping through a photo album, but instead of pictures, you're looking at the highlights of your code's journey. With a simple command like git tag, you can see all the tags, sort of like having a bird's eye view of your project's timeline. It's fascinating when you use git show [tag-name] and get a glimpse into the past, seeing what changes were made at that specific point. It's like a time machine for your code! This feature is super handy for understanding the evolution of your project and making sure you're always on top of your game.

Pushing and pulling Git tags is crucial for team collaboration, akin to sharing an updated map of your project. By pushing tags (git push origin [tag-name]), you're broadcasting key milestones to your team. Conversely, pulling tags updates your map with others' markers. This practice keeps everyone aligned and informed about the project's progress, ensuring all are on the same page, or rather, the same commit!

Deleting and renaming Git tags is like housekeeping for your codebase. Imagine your repository as a garden, and tags are the labels on your plants. Sometimes, you need to pull out the old, incorrect labels (deleting tags) or maybe just update them to better reflect what's growing (renaming tags). With a few commands, you can easily remove outdated or incorrect tags (git tag -d [tag-name]) or rename them, which is actually a two-step dance of creating a new tag and deleting the old one. It's a bit like pruning and relabeling in the garden, ensuring everything is tidy and accurately named.