We can also sort the tags from the tag command. An example output is as shown: v6.1.0-preview.1 The command above should return the preview tags. In that case, we can use the -l option and pass the desired pattern.Īn example is as shown: $ git tag -l *preview* In some cases, you may only want to fetch the tags that match a specific pattern. SD/717473 Integrate changes from SD between and
Git tag history update#
SD/715912 Update files from Source Depot changeset SD/709776 Update files from Source Depot changeset SD/706766 Update files from Source Depot changeset SD/704605 Update files from Source Depot changeset SD/700586 Update files from Source Depot changeset SD/695331 Update files from psl-monad source-depot Resulting output: Advertisements SD/688741 Move files from psl-monad submodule to super-project To get an extensive description of the tags list, we can use -n option to the git tag command as shown: $ git tag -n The command should return the tags available in the current repository as: SD/688741 To view the tags in a local repository, we can use the git tag command with no arguments: Advertisements $ git tag
They serve as permanent markers and are not intended to change over time, unlike branches that can move as new commits are added. Tags are typically used to provide a human-readable and memorable identifier for a specific commit, making it easier to refer to that commit later. It is commonly used to mark significant points in a project's development, such as releases, milestones, or important commits. A Git tag is a named reference to a specific commit in a repository's history.
0 kommentar(er)
