blocks|key|1466193|text|你可以看看git+describe，它做的事情和你所要求的很接近。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1466194|entityMap^0|5|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You could take a look at <code>git describe</code>, which does something close to what you're asking.

blocks|key|1466263|text|要获取最新的标记(后面的示例输出)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466264|git+describe+--tags+--abbrev=0+++#+0.1.0-dev|code-block|syntax|javascript|1466265|要获得最新的标记，以及标记对象顶部的额外提交次数，请执行更多操作：|1466266|git+describe+--tags++++++++++++++#+0.1.0-dev-93-g1416689|1466267|要获取最新的带注释的标记，请执行以下操作：|1466268|git+describe+--abbrev=0|1466269|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

To get the most recent tag (example output afterwards):
<pre><code>git describe --tags --abbrev=0 # 0.1.0-dev
</code></pre>
To get the most recent tag, with the number of additional commits on top of the tagged object &amp; more:
<pre><code>git describe --tags # 0.1.0-dev-93-g1416689
</code></pre>
To get the most recent annotated tag:
<pre><code>git describe --abbrev=0
</code></pre>

blocks|key|1466292|text|将输出所有分支的最新标记提交的标记|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466293|git+describe+--tags+$(git+rev-list+--tags+--max-count=1)|code-block|syntax|javascript|1466294|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Will output the tag of the latest tagged commit across all branches

<pre><code>git describe --tags $(git rev-list --tags --max-count=1)
</code></pre>

blocks|key|1466236|text|这个怎么样？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466237|TAG=$(git+describe+$(git+rev-list+--tags+--max-count=1))|offset|length|style|CODE|1466238|从技术上讲，不一定会得到最新的标记，但会得到标记的最新提交，这可能是也可能不是你正在寻找的东西。|1466239|entityMap^0|0|0|1K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

How about this?

<code>TAG=$(git describe $(git rev-list --tags --max-count=1))</code>

Technically, won't necessarily get you the latest tag, but the latest commit which is tagged, which may or may not be the thing you're looking for.

blocks|key|1466866|text|您可以在此处执行：git+describe+--tags+$(git+rev-list+--tags+--max-count=1)+talked：How+to+get+latest+tag+name?|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1466867|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4277773/how-to-get-latest-tag-name?noredirect=1&lq=1^0|9|1K|21|R|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

You can execute: <code>git describe --tags $(git rev-list --tags --max-count=1)</code> talked here: <a href="https://stackoverflow.com/questions/4277773/how-to-get-latest-tag-name?noredirect=1&amp;lq=1">How to get latest tag name?</a>

blocks|key|296607|text|git+describe+--tags|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|296608|返回当前分支所能看到的最后一个标记|296609|entityMap^0|0|J|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

<code>git describe --tags</code>

returns the last tag able to be seen by current branch

blocks|key|61839|text|“最新的”在git方面可能有两种含义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61840|你的意思可能是，“哪个标签的创建日期在时间上最晚”，这里的大多数答案都是针对这个问题的。就您的问题而言，您可能希望返回标记c。|offset|length|style|CODE|61841|或者你可以说“哪个标签在开发历史上最接近某个指定的分支”，通常是你所在的分支，HEAD。在您的问题中，这将返回标记a。|61842|当然，这些可能是不同的：|61843|A->B->C->D->E->F+(HEAD)
+++++++\+++++\
++++++++\+++++X->Y->Z+(v0.2)
+++++++++P->Q+(v0.1)|code-block|syntax|javascript|61844|想象一下，开发人员在周一将Z标记为v0.2，然后在周二将Q标记为v0.1。v0.1是较新的，但v0.2在开发历史上更接近HEAD，从某种意义上说，它所在的道路是从更接近HEAD的点开始的。|61845|我认为您通常会想要第二个答案，更接近开发历史。你可以通过对每个标签使用git+log+v0.2..HEAD等来找出答案。这给出了HEAD上的提交次数，因为在v0.2结束的路径与HEAD后面的路径不同。|61846|以下是一个Python脚本，它通过迭代运行此检查的所有标签，然后打印出头上提交次数最少的标签，因为标签路径出现了分歧：|61847|https://github.com/MacPython/terryfy/blob/master/git-closest-tag|61848|git+describe做了一些略微不同的事情，因为它从(例如)HEAD以查找位于从HEAD返回历史的路径上的第一个标记。在git术语中，git+describe查找从HEAD“可达”的标签。因此，它不会找到像v0.2这样的标签，这些标签不在从HEAD返回的路径上，而是从那里分叉出来的路径。|61849|entityMap|0|LINK|mutability|MUTABLE|url^0|0|1P|1|0|13|4|1L|1|0|0|0|D|1|H|4|S|1|W|4|11|4|1B|4|0|Z|I|26|4|0|0|0|1S|0|0|0|C|1X|C|2X|4|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1H|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1I|8|@$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]|$D|1P|E|1Q|F|G]|$D|1R|E|1S|F|G]|$D|1T|E|1U|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1V|8|@$D|1W|E|1X|F|G]|$D|1Y|E|1Z|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|20|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|21|8|@]|9|@$D|22|E|23|1|24]]|A|$]]|$1|Y|3|Z|5|6|7|25|8|@$D|26|E|27|F|G]|$D|28|E|29|F|G]|$D|2A|E|2B|F|G]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|X]]]]

"Most recent" could have two meanings in terms of git.

You could mean, "which tag has the creation date latest in time", and most of the answers here are for that question. In terms of your question, you would want to return tag <code>c</code>. 

Or you could mean "which tag is the closest in development history to some named branch", usually the branch you are on, <code>HEAD</code>. In your question, this would return tag <code>a</code>.

These might be different of course:

<pre><code>A-&gt;B-&gt;C-&gt;D-&gt;E-&gt;F (HEAD)
 \ \
 \ X-&gt;Y-&gt;Z (v0.2)
 P-&gt;Q (v0.1)
</code></pre>

Imagine the developer tag'ed <code>Z</code> as <code>v0.2</code> on Monday, and then tag'ed <code>Q</code> as <code>v0.1</code> on Tuesday. <code>v0.1</code> is the more recent, but <code>v0.2</code> is closer in development history to HEAD, in the sense that the path it is on starts at a point closer to HEAD.

I think you usually want this second answer, closer in development history. You can find that out by using <code>git log v0.2..HEAD</code> etc for each tag. This gives you the number of commits on HEAD since the path ending at <code>v0.2</code> diverged from the path followed by HEAD.

Here's a Python script that does that by iterating through all the tags running this check, and then printing out the tag with fewest commits on HEAD since the tag path diverged:

<a href="https://github.com/MacPython/terryfy/blob/master/git-closest-tag">https://github.com/MacPython/terryfy/blob/master/git-closest-tag</a>

<code>git describe</code> does something slightly different, in that it tracks back from (e.g.) HEAD to find the first tag that is on a path back in the history from HEAD. In git terms, <code>git describe</code> looks for tags that are "reachable" from HEAD. It will therefore not find tags like <code>v0.2</code> that are not on the path back from HEAD, but a path that diverged from there.

blocks|key|61863|text|git+describe+--abbrev=0+--tags|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|61864|如果您没有看到最新的标签，请确保在运行之前获取源：|unstyled|61865|git+remote+update|61866|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>git describe --abbrev=0 --tags
</code></pre>
If you don't see latest tag, make sure of fetching origin before running that:
<pre><code>git remote update
</code></pre>

blocks|key|1598701|text|我不确定为什么这个问题没有答案。即所有标签(包括无注释的标签)，且不带后缀：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1598702|git+describe+--tags+--abbrev=0|code-block|syntax|javascript|1598703|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm not sure why there are no answers to what the question is asking for. i.e. All tags (non-annotated included) and without the suffix:
<pre><code>git describe --tags --abbrev=0
</code></pre>

blocks|key|296693|text|对于所有建议(除了Matthew+Brett解释之外，此答案帖子的最新版本)有什么问题？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|296694|当你在不同的历史点上使用jQuery可视化标签历史表示检查结果时，只需运行其他人提供的关于+Git历史的任何命令(I+did，这就是为什么你看到这篇文章)：|style|BOLD|296695|$+git+log+--graph+--all+--decorate+--oneline+--simplify-by-decoration|code-block|syntax|javascript|296696|如今，许多项目在与主线分开的分支中执行版本(以及标记)。|296697|对此有很强的理由。只要看看任何成熟的JS/CSS项目就可以了。对于用户约定，它们在DVCS中提供二进制/精简版本文件。作为项目维护者，您自然不希望用无用的二进制blob来丢弃您的主线差异历史，并在主线之外执行构建工件的提交。|296698|因为Git使用DAG而不是线性历史-很难定义距离度量，所以我们可以说-哦，rev是最接近我的HEAD的！|CODE|296699|我开始了我自己的旅程(看看里面，我没有在这篇长文中复制奇特的证明图片)：|296700|What+is+nearest+tag+in+the+past+with+respect+to+branching+in+Git?|296701|目前，我有4个合理的定义，标签和修订之间的距离，随着有用性的下降：|296702|从tag|296703|number到合并基的最短路径的|unordered-list-item|296704|length，以及从的HEAD到合并基的合并基的|296705|length，该最短路径可从标头到达，但不能从标签的标签头到达，而不管合并基|296706|296707|296708|296709|我不知道如何计算最短路径的长度。|296710|根据HEAD和tag之间的合并基的date对标签进行排序的脚本：|296711|$+git+tag+\
+++++%7C+while+read+t;+do+\
+++++++++b=`git+merge-base+HEAD+$t`;+\
+++++++++echo+`git+log+-n+1+$b+--format=%25ai`+$t;+\
+++++++done+%7C+sort|296712|它在大多数项目中都可用。|296713|根据可从HEAD到达但无法从tag到达的转数对标签进行排序的脚本：|296714|$+git+tag+\
++++%7C+while+read+t;+do+echo+`git+rev-list+--count+$t..HEAD`+$t;+done+\
++++%7C+sort+-n|296715|如果你的项目历史记录有奇怪的提交日期(因为改写数据库、重写历史记录，或者一些笨蛋忘记更换BIOS电池，或者你在历史记录上使用的其他魔法)，那么可以使用上面的脚本。|296716|For+last选项(+date++of+tag，不考虑合并基准)要获得按日期排序的标签列表，请使用：|296717|$+git+log+--tags+--simplify-by-decoration+--pretty="format:%25ci+%25d"+%7C+sort+-r|296718|要获取已知的当前修订日期，请使用：|296719|$+git+log+--max-count=1|296720|请注意，git+describe+--tags有自己的用例，但不用于在项目历史中查找人类期望最近的标签。|296721|注意你可以在任何版本上使用上面的方法，只需用你想要的替换HEAD即可！|296722|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/24557377/173149|1|https://stackoverflow.com/questions/33530606/what-is-nearest-tag-in-the-past-with-respect-to-branching-in-git^0|9|D|0|0|19|X|0|0|0|B|R|1|0|30|4|0|0|Q|1A|4|0|0|0|1T|1|0|0|0|0|G|0|0|O|B|4|1|0|12|1|0|0|0|0|G|0|0|W|2|4|0|0|0|C|0|0|X|0|0|0|29|0|0|1F|0|0|0|H|0|0|0|13|16|A|4|J|0|0|Z|S|4|0^^$0|@$1|2|3|4|5|6|7|2B|8|@]|9|@$A|2C|B|2D|1|2E]]|C|$]]|$1|D|3|E|5|6|7|2F|8|@$A|2G|B|2H|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|2I|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|2J|8|@$A|2K|B|2L|F|G]|$A|2M|B|2N|F|G]]|9|@]|C|$]]|$1|O|3|P|5|6|7|2O|8|@$A|2P|B|2Q|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|2R|8|@$A|2S|B|2T|F|G]|$A|2U|B|2V|F|S]]|9|@]|C|$]]|$1|T|3|U|5|6|7|2W|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|2X|8|@]|9|@$A|2Y|B|2Z|1|30]]|C|$]]|$1|X|3|Y|5|6|7|31|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|32|8|@]|9|@]|C|$]]|$1|11|3|12|5|13|7|33|8|@$A|34|B|35|F|G]]|9|@]|C|$]]|$1|14|3|15|5|13|7|36|8|@$A|37|B|38|F|G]|$A|39|B|3A|F|S]]|9|@]|C|$]]|$1|16|3|17|5|13|7|3B|8|@$A|3C|B|3D|F|G]]|9|@]|C|$]]|$1|18|3|-4|5|6|7|3E|8|@]|9|@]|C|$]]|$1|19|3|-4|5|6|7|3F|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|3G|8|@]|9|@]|C|$]]|$1|1B|3|1C|5|6|7|3H|8|@$A|3I|B|3J|F|G]]|9|@]|C|$]]|$1|1D|3|1E|5|6|7|3K|8|@$A|3L|B|3M|F|G]|$A|3N|B|3O|F|S]]|9|@]|C|$]]|$1|1F|3|1G|5|J|7|3P|8|@]|9|@]|C|$K|L]]|$1|1H|3|1I|5|6|7|3Q|8|@$A|3R|B|3S|F|G]]|9|@]|C|$]]|$1|1J|3|1K|5|6|7|3T|8|@$A|3U|B|3V|F|G]]|9|@]|C|$]]|$1|1L|3|1M|5|J|7|3W|8|@]|9|@]|C|$K|L]]|$1|1N|3|1O|5|6|7|3X|8|@$A|3Y|B|3Z|F|G]]|9|@]|C|$]]|$1|1P|3|1Q|5|6|7|40|8|@$A|41|B|42|F|G]]|9|@]|C|$]]|$1|1R|3|1S|5|J|7|43|8|@]|9|@]|C|$K|L]]|$1|1T|3|1U|5|6|7|44|8|@$A|45|B|46|F|G]]|9|@]|C|$]]|$1|1V|3|1W|5|J|7|47|8|@]|9|@]|C|$K|L]]|$1|1X|3|1Y|5|6|7|48|8|@$A|49|B|4A|F|G]|$A|4B|B|4C|F|G]|$A|4D|B|4E|F|S]]|9|@]|C|$]]|$1|1Z|3|20|5|6|7|4F|8|@$A|4G|B|4H|F|G]|$A|4I|B|4J|F|S]]|9|@]|C|$]]|$1|21|3|-4|5|6|7|4K|8|@]|9|@]|C|$]]]|22|$23|$5|24|25|26|C|$27|28]]|29|$5|24|25|26|C|$27|2A]]]]

What is wrong with all suggestions (except <a href="https://stackoverflow.com/a/24557377/173149">Matthew Brett</a> explanation, up to date of this answer post)?

Just run any command supplied by other on jQuery Git history when you at different point of history and check result with visual tagging history representation (I did that is why you see this post):

<pre><code>$ git log --graph --all --decorate --oneline --simplify-by-decoration
</code></pre>

Todays many project perform releases (and so tagging) in separate branch from mainline.

There are strong reason for this. Just look to any well established JS/CSS projects. For user conventions they carry binary/minified release files in DVCS. Naturally as project maintainer you don't want to garbage your mainline diff history with useless binary blobs and perform commit of build artifacts out of mainline.

Because Git uses DAG and not linear history - it is hard to define distance metric so we can say - oh that rev is most nearest to my <code>HEAD</code>!

I start my own journey in (look inside, I didn't copy fancy proof images to this long post):

<a href="https://stackoverflow.com/questions/33530606/what-is-nearest-tag-in-the-past-with-respect-to-branching-in-git">What is nearest tag in the past with respect to branching in Git?</a>

Currently I have 4 reasonable definition of distance between tag and revision with decreasing of usefulness:

<ul>
<li>length of shortest path from <code>HEAD</code> to merge base with tag</li>
<li>date of merge base between <code>HEAD</code> and tag</li>
<li>number of revs that reachable from HEAD but not reachable from tag</li>
<li>date of tag regardless merge base</li>
</ul>

I don't know how to calculate length of shortest path.

Script that sort tags according to date of merge base between <code>HEAD</code> and tag:

<pre><code>$ git tag \
 | while read t; do \
 b=`git merge-base HEAD $t`; \
 echo `git log -n 1 $b --format=%ai` $t; \
 done | sort
</code></pre>

It usable on most of projects.

Script that sort tags according to number of revs that reachable from HEAD but not reachable from tag:

<pre><code>$ git tag \
 | while read t; do echo `git rev-list --count $t..HEAD` $t; done \
 | sort -n
</code></pre>

If your project history have strange dates on commits (because of rebases or another history rewriting or some moron forget to replace BIOS battery or other magics that you do on history) use above script.

For last option (date of tag regardless merge base) to get list of tags sorted by date use:

<pre><code>$ git log --tags --simplify-by-decoration --pretty="format:%ci %d" | sort -r
</code></pre>

To get known current revision date use:

<pre><code>$ git log --max-count=1
</code></pre>

Note that <code>git describe --tags</code> have usage on its own cases but not for finding human expected nearest tag in project history.

NOTE You can use above recipes on any revision, just replace <code>HEAD</code> with what you want!

blocks|key|1466912|text|git+tag+--sort=committerdate+%7C+tail+-1|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1466913|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>git tag --sort=committerdate | tail -1
</code></pre>

blocks|key|1466385|text|git+log+--tags+--no-walk+--pretty="format:%25d"+%7C+sed+2q+%7C+sed+'s/[()]//g'+%7C+sed+s/,[%5E,]*$//+%7C+sed++'s+......++'|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1466386|如果需要多个最后一个标记，则为|unstyled|1466387|(git+describe+--标签有时会给出错误的散列，我不知道为什么，但对我来说--max-count+2不起作用)|offset|length|style|BOLD|1466388|这就是你如何以相反的时间顺序获得最新的2个标签名称的列表，在git+1.8.4上工作得很好。对于较早版本的git(如1.7.*)，输出中没有"tag：“字符串-只需删除最后一次sed调用|1466389|如果你想要2个以上的最新标签--把这个"sed+2q“改成"sed+5q”或者你需要的任何东西|1466390|然后，您可以轻松地将每个标记名解析为变量或变量。|1466391|entityMap^0|0|0|0|1O|0|0|2L|0|0|1B|0|0|O|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|F|7|Z|8|@$I|10|J|11|K|L]]|9|@]|A|$]]|$1|O|3|P|5|F|7|12|8|@$I|13|J|14|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|15|8|@$I|16|J|17|K|L]]|9|@]|A|$]]|$1|S|3|-4|5|F|7|18|8|@]|9|@]|A|$]]]|T|$]]

<pre><code>git log --tags --no-walk --pretty="format:%d" | sed 2q | sed 's/[()]//g' | sed s/,[^,]*$// | sed 's ...... '
</code></pre>

IF YOU NEED MORE THAN ONE LAST TAG

(git describe --tags sometimes gives wrong hashes, i dont know why, but for me --max-count 2 doesnt work)

this is how you can get list with latest 2 tag names in reverse chronological order, works perfectly on git 1.8.4. 
For earlier versions of git(like 1.7.*), there is no "tag: " string in output - just delete last sed call

If you want more than 2 latest tags - change this "sed 2q" to "sed 5q" or whatever you need

Then you can easily parse every tag name to variable or so.

blocks|key|1466620|text|git+tag+-l+ac*+%7C+tail+-n1|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1466621|获取带有前缀"ac"的最后一个标记。例如，使用ac1.0.0或ac1.0.5命名的标记。其他名为1.0.0、1.1.0的标记将被忽略。|unstyled|offset|length|style|BOLD|CODE|1466622|git+tag+-l+[0-9].*+%7C+tail+-n1|1466623|获取最后一个标记，它的第一个字符是0-9。因此，那些带有第一个字符a-z的标记将被忽略。|1466624|更多信息|1466625|git+tag+--help+#+Help+for+`git+tag`|1466626|1466627|git+tag+-l+<pattern>|1466628|1466629|列出名称与给定模式匹配的标记(如果没有给定模式，则为all+)。运行不带参数的"git+tag“也会列出所有的标签。模式是一个外壳通配符(即，使用fnmatch(3)匹配)。可以给出多个模式；如果它们中的任何一个匹配，则显示标记。|blockquote|1466630|1466631|1466632|1466633|tail+-n+<number>+#+display+the+last+part+of+a+file
tail+-n1+#+Display+the+last+item+|1466634|1466635|更新|1466636|在git+tag+--help中，关于sort参数。如果tag.sort属性不存在，它将默认使用lexicorgraphic+order。|1466637|1466638|排序顺序默认为为tag.sort变量配置的值(如果存在)，否则为字典顺序。参见git-config(1)。|1466639|1466640|1466641|在谷歌之后，someone+said+git+2.8.0支持以下语法。|1466642|git+tag+--sort=committerdate|1466643|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/36636526/419348^0|0|6|4|N|7|V|7|1C|5|1I|5|0|0|H|3|X|3|0|0|0|0|0|0|0|0|0|0|0|0|0|1|E|J|4|S|8|1C|K|0|0|0|0|0|6|C|0|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|1S|8|@$G|1T|H|1U|I|J]|$G|1V|H|1W|I|K]|$G|1X|H|1Y|I|K]|$G|1Z|H|20|I|K]|$G|21|H|22|I|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|23|8|@]|9|@]|A|$B|C]]|$1|N|3|O|5|F|7|24|8|@$G|25|H|26|I|K]|$G|27|H|28|I|K]]|9|@]|A|$]]|$1|P|3|Q|5|F|7|29|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|2A|8|@]|9|@]|A|$B|C]]|$1|T|3|-4|5|F|7|2B|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2C|8|@]|9|@]|A|$B|C]]|$1|W|3|-4|5|F|7|2D|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Z|7|2E|8|@]|9|@]|A|$]]|$1|10|3|-4|5|F|7|2F|8|@]|9|@]|A|$]]|$1|11|3|-4|5|F|7|2G|8|@]|9|@]|A|$]]|$1|12|3|-4|5|F|7|2H|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2I|8|@]|9|@]|A|$B|C]]|$1|15|3|-4|5|F|7|2J|8|@]|9|@]|A|$]]|$1|16|3|17|5|F|7|2K|8|@]|9|@]|A|$]]|$1|18|3|19|5|F|7|2L|8|@$G|2M|H|2N|I|K]|$G|2O|H|2P|I|K]|$G|2Q|H|2R|I|K]|$G|2S|H|2T|I|K]]|9|@]|A|$]]|$1|1A|3|-4|5|F|7|2U|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|Z|7|2V|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|F|7|2W|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|F|7|2X|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|F|7|2Y|8|@]|9|@$G|2Z|H|30|1|31]]|A|$]]|$1|1H|3|1I|5|6|7|32|8|@]|9|@]|A|$B|C]]|$1|1J|3|-4|5|F|7|33|8|@]|9|@]|A|$]]]|1K|$1L|$5|1M|1N|1O|A|$1P|1Q]]]]

<pre><code>git tag -l ac* | tail -n1
</code></pre>

Get the last tag with prefix "ac". For example, tag named with <code>ac1.0.0</code>, or <code>ac1.0.5</code>. Other tags named <code>1.0.0</code>, <code>1.1.0</code> will be ignored.

<pre><code>git tag -l [0-9].* | tail -n1
</code></pre>

Get the last tag, whose first char is <code>0-9</code>. So, those tags with first char <code>a-z</code> will be ignored.

<h2>More info</h2>

<pre><code>git tag --help # Help for `git tag`
</code></pre>

<hr>

<pre><code>git tag -l &lt;pattern&gt;
</code></pre>

<blockquote>
 List tags with names that match the given pattern (or all if no
 pattern is given). Running "git tag" without arguments also lists
 all tags. The pattern is a shell wildcard (i.e., matched using
 fnmatch(3)). Multiple patterns may be given; if any of them
 matches, the tag is shown.
</blockquote>

<hr>

<pre><code>tail -n &lt;number&gt; # display the last part of a file
tail -n1 # Display the last item 
</code></pre>

<hr>

<h2>Update</h2>

With <code>git tag --help</code>, about the <code>sort</code> argument. It will use <code>lexicorgraphic order</code> by default, if <code>tag.sort</code> property doesn't exist.

<blockquote>
 Sort order
 defaults to the value configured for the tag.sort variable if it
 exists, or lexicographic order otherwise. See git-config(1).
</blockquote>

After google, <a href="https://stackoverflow.com/a/36636526/419348">someone said</a> git 2.8.0 support following syntax.

<pre><code>git tag --sort=committerdate
</code></pre>

blocks|key|1598736|text|CI/CD进程中describe的问题是您可能会遇到fatal:+no+tags+can+describe错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1598737|发生这种情况是因为，根据git+describe+--help|1598738|1598739|该命令查找可从提交中访问的最新标记。|blockquote|BOLD|1598740|1598741|1598742|如果您想要存储库中的最新标记，而不管您所在的分支是否可以到达该标记，通常是因为它不是当前分支的树的一部分，则此命令将为您提供整个存储库中最近创建的标记：|1598743|git+tag+-l+--sort=-creatordate+%7C+head+-n+1|code-block|syntax|javascript|1598744|entityMap^0|8|8|Q|R|0|C|J|0|0|A|8|0|0|0|0|24|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|16|8|@$9|17|A|18|B|L]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1B|8|@$9|1C|A|1D|B|L]]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1E|8|@]|D|@]|E|$T|U]]|$1|V|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|W|$]]

The problem with <code>describe</code> in CI/CD processes is you can run into the <code>fatal: no tags can describe</code> error.
This will occur because, per <code>git describe --help</code>:
<blockquote>
The command finds the most recent tag that is reachable from a commit.
</blockquote>
If you want the latest tag in the repo, regardless if the branch you are on can reach the tag, typically because it is not part of the current branch's tree, this command will give you the most recently created tag in the entire repo:
<pre><code>git tag -l --sort=-creatordate | head -n 1
</code></pre>

blocks|key|1466345|text|如果您需要最后两个标签(例如，为了生成当前标签和前一个标签之间的更改日志)，以下方法适用于我。我只在最新的标签是HEAD的情况下测试过它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1466346|PreviousAndCurrentGitTag=`git+describe+--tags+\`git+rev-list+--tags+--abbrev=0+--max-count=2\`+--abbrev=0`
PreviousGitTag=`echo+$PreviousAndCurrentGitTag+%7C+cut+-f+2+-d+'+'`
CurrentGitTag=`echo+$PreviousAndCurrentGitTag+%7C+cut+-f+1+-d+'+'`

GitLog=`git+log+${PreviousGitTag}..${CurrentGitTag}+--pretty=oneline+%7C+sed+"s_.\{41\}$.*$_;+\1_"`|code-block|syntax|javascript|1466347|它适合我的需要，但由于我不是git专家，我相信它还可以进一步改进。我还怀疑它会在提交历史记录向前移动的情况下崩溃。我只是分享一下，以防对别人有帮助。|1466348|entityMap^0|1K|4|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

The following works for me in case you need last two tags (for example, in order to generate change log between current tag and the previous tag). I've tested it only in situation where the latest tag was the <code>HEAD</code>.

<pre><code>PreviousAndCurrentGitTag=`git describe --tags \`git rev-list --tags --abbrev=0 --max-count=2\` --abbrev=0`
PreviousGitTag=`echo $PreviousAndCurrentGitTag | cut -f 2 -d ' '`
CurrentGitTag=`echo $PreviousAndCurrentGitTag | cut -f 1 -d ' '`

GitLog=`git log ${PreviousGitTag}..${CurrentGitTag} --pretty=oneline | sed "s_.\{41\}$.*$_; \1_"`
</code></pre>

It suits my needs, but as I'm no git wizard, I'm sure it could be further improved. I also suspect it will break in case the commit history moves forward. I'm just sharing in case it helps someone.

blocks|key|296886|text|如果您需要一个用于获取当前分支上的最新标记名称+(by+tag+date)的one+liner|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|296887|git+for-each-ref+refs/tags+--sort=-taggerdate+--format=%25(refname:short)+--count=1+--points-at=HEAD|code-block|syntax|javascript|296888|我们使用它来设置设置中的版本号。|296889|输出示例：|296890|v1.0.0|296891|也可以在Windows上运行。|296892|entityMap^0|B|4|H|6|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|13|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

If you need a one liner which gets the latest tag name (by tag date) on the current branch:

<pre><code>git for-each-ref refs/tags --sort=-taggerdate --format=%(refname:short) --count=1 --points-at=HEAD
</code></pre>

We use this to set the version number in the setup.

Output example:

<pre><code>v1.0.0
</code></pre>

Works on Windows, too.

blocks|key|61483|text|我的第一个想法是，您可以使用git+rev-list+HEAD，它按时间倒序列出所有转速，并与git+tag+--contains结合使用。当您找到git+tag+--contains生成非空列表的ref时，您就找到了最新的标记。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|61484|entityMap^0|E|H|1B|I|22|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

My first thought is you could use <code>git rev-list HEAD</code>, which lists all the revs in reverse chronological order, in combination with <code>git tag --contains</code>. When you find a ref where <code>git tag --contains</code> produces a nonempty list, you have found the most recent tag(s).

blocks|key|296836|text|如果要查找应用于特定分支的最后一个标记，可以尝试以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|296837|git+describe+--tag+$(git+rev-parse+--verify+refs/remotes/origin/"branch_name")|code-block|syntax|javascript|296838|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you want to find the last tag that was applied on a specific branch you can try the following:

<pre><code>git describe --tag $(git rev-parse --verify refs/remotes/origin/"branch_name")
</code></pre>

blocks|key|62046|text|这是一个古老的主题，但似乎很多人错过了OP问题的最简单、最容易和最正确的答案:要获得当前分支的最新标记，请使用git+describe+HEAD。好了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|62047|编辑:你也可以提供任何有效的引用名，甚至是远程的；也就是说，git+describe+origin/master会告诉你可以从源/主站到达的最新标签。|62048|entityMap^0|16|4|1J|H|0|U|Q|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|P|8|@$9|Q|A|R|B|D]]|E|@]|F|$]]|$1|I|3|-4|5|6|7|S|8|@]|E|@]|F|$]]]|J|$]]

This is an old thread, but it seems a lot of people are missing the simplest, easiest, and most correct answer to OP's question: to get the latest tag for the current branch, you use <code>git describe HEAD</code>. Done.

Edit: you can also supply any valid refname, even remotes; i.e., <code>git describe origin/master</code> will tell you the latest tag that can be reached from origin/master.

blocks|key|1467009|text|git+tag+--sort=-refname+%7C+awk+'match($0,+/%5E[0-9]%2B\.[0-9]%2B\.[0-9]%2B$/)'+%7C+head+-n+1+|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1467010|这个标签跨所有匹配语义版本控制的分支获取最新标记。|unstyled|1467011|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>git tag --sort=-refname | awk 'match($0, /^[0-9]+\.[0-9]+\.[0-9]+$/)' | head -n 1 
</code></pre>
This one gets the latest tag across all branches that matches Semantic Versioning.

blocks|key|1466743|text|为了仅获取当前分支/以当前分支为前缀的标记名称的最新标记，我必须执行以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466744|BRANCH=`git+rev-parse+--abbrev-ref+HEAD`+&&+git+describe+--tags+--abbrev=0+$BRANCH%5E+%7C+grep+$BRANCH|code-block|syntax|javascript|1466745|1466746|+分支主机：|blockquote|offset|length|style|BOLD|1466747|1466748|1466749|git+checkout+master

BRANCH=`git+rev-parse+--abbrev-ref+HEAD`+&&+git+describe+--tags+
--abbrev=0+$BRANCH%5E+%7C+grep+$BRANCH

master-1448|1466750|1466751|+分支自定义：|1466752|1466753|1466754|git+checkout+9.4

BRANCH=`git+rev-parse+--abbrev-ref+HEAD`+&&+git+describe+--tags+
--abbrev=0+$BRANCH%5E+%7C+grep+$BRANCH

9.4-6|1466755|最后，我需要递增并获取标签%2B1，用于下一个标签。|1466756|BRANCH=`git+rev-parse+--abbrev-ref+HEAD`+&&+git+describe+--tags++--abbrev=0+$BRANCH%5E+%7C+grep+$BRANCH+%7C+awk+-F-+'{print+$NF}'|1466757|entityMap^0|0|0|0|1|5|0|0|0|0|0|1|6|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|18|8|@$K|19|L|1A|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|T|3|U|5|J|7|1F|8|@$K|1G|L|1H|M|N]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|X|3|Y|5|D|7|1K|8|@]|9|@]|A|$E|F]]|$1|Z|3|10|5|6|7|1L|8|@]|9|@]|A|$]]|$1|11|3|12|5|D|7|1M|8|@]|9|@]|A|$E|F]]|$1|13|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|14|$]]

To get the latest tag only on the current branch/tag name that prefixes with current branch, I had to execute the following

<pre><code>BRANCH=`git rev-parse --abbrev-ref HEAD` &amp;&amp; git describe --tags --abbrev=0 $BRANCH^ | grep $BRANCH
</code></pre>

<blockquote>
 Branch master: 
</blockquote>

<pre><code>git checkout master

BRANCH=`git rev-parse --abbrev-ref HEAD` &amp;&amp; git describe --tags 
--abbrev=0 $BRANCH^ | grep $BRANCH

master-1448
</code></pre>

<blockquote>
 Branch custom: 
</blockquote>

<pre><code>git checkout 9.4

BRANCH=`git rev-parse --abbrev-ref HEAD` &amp;&amp; git describe --tags 
--abbrev=0 $BRANCH^ | grep $BRANCH

9.4-6
</code></pre>

And my final need to increment and get the tag +1 for next tagging.

<pre><code>BRANCH=`git rev-parse --abbrev-ref HEAD` &amp;&amp; git describe --tags --abbrev=0 $BRANCH^ | grep $BRANCH | awk -F- '{print $NF}'
</code></pre>

blocks|key|1596522|text|对于所问的问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1596523|1596524|如何获取当前分支最新的标签名|blockquote|1596525|1596526|1596527|你想要的|1596528|git+log+--first-parent+--pretty=%25d+%7C+grep+-m1+tag:|code-block|syntax|javascript|1596529|--first-parent告诉git+log不要详细说明任何合并的历史，--pretty=%25d说只显示修饰，即任何提交的本地名称。grep+-m1说“只匹配一个”，所以你只会得到最新的标签。|offset|length|style|CODE|1596530|entityMap^0|0|0|0|0|0|0|0|0|E|G|7|11|B|1U|8|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|13|8|@$Q|14|R|15|S|T]|$Q|16|R|17|S|T]|$Q|18|R|19|S|T]|$Q|1A|R|1B|S|T]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|V|$]]

For the question as asked,

<blockquote>
 How to get the latest tag name in the current branch
</blockquote>

you want

<pre><code>git log --first-parent --pretty=%d | grep -m1 tag:
</code></pre>

<code>--first-parent</code> tells <code>git log</code> not to detail any merged histories, <code>--pretty=%d</code> says to show only the decorations i.e. local names for any commits. <code>grep -m1</code> says "match just one", so you get just the most-recent tag.

blocks|key|62180|text|如果您的标签是可排序的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|62181|git+tag+--merged+$YOUR_BRANCH_NAME+%7C+grep+"prefix/"+%7C+sort+%7C+tail+-n+1|code-block|syntax|javascript|62182|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

if your tags are sortable:

<pre><code>git tag --merged $YOUR_BRANCH_NAME | grep "prefix/" | sort | tail -n 1
</code></pre>

blocks|key|296672|text|这里没有提到太多未注释的标记与带注释的标记。“‘describe”适用于带注释的标签，并忽略未注释的标签。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|296673|这看起来很丑陋，但它确实完成了请求的任务，并且在其他分支上找不到任何标记(并且不会在下面示例中的命令:+master中指定的分支上找到任何标记)|296674|过滤应该是优化(合并)的，但同样，这似乎是工作。|296675|git+log++--decorate+--tags+master+%7Cgrep+'%5Ecommit'%7Cgrep+'tag:.*)$'%7Cawk+'{print+$NF}'%7Csed+'s/)$//'%7Chead+-n+1|code-block|syntax|javascript|296676|欢迎评论，因为我现在要将其用于:)|296677|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Not much mention of unannotated tags vs annotated ones here. 'describe' works on annotated tags and ignores unannotated ones. 

This is ugly but does the job requested and it will not find any tags on other branches (and not on the one specified in the command: master in the example below)

The filtering should prob be optimized (consolidated), but again, this seems to the the job.

<pre><code>git log --decorate --tags master |grep '^commit'|grep 'tag:.*)$'|awk '{print $NF}'|sed 's/)$//'|head -n 1
</code></pre>

Critiques welcome as I am going now to put this to use :)

What's the simplest way to get the most recent tag in Git?

<pre><code>git tag a HEAD
git tag b HEAD^^
git tag c HEAD^
git tag
</code></pre>

output:

<pre><code>a
b
c
</code></pre>

Should I write a script to get each tag's datetime and compare them?

How can I get the latest tag name in current branch in Git?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在Git中获取最新标签的最简单方法是什么？git tag a HEADgit tag b HEAD^^git tag c HEAD^git tag输出：abc我是否应该编写一个脚本来获取每个标记的日期时间并对它们进行比较？

问如何在Git中获取当前分支的最新标签名称？
EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Git中获取当前分支的最新标签名称？EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Git中获取当前分支的最新标签名称？
EN