blocks|key|4095853|text|使用git+rev-list+--max-count=1+HEAD|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4095854|entityMap^0|2|V|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|$]]

Use <code>git rev-list --max-count=1 HEAD</code>

blocks|key|4095879|text|要将任意扩展对象引用转换为SHA-1，只需使用，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4095880|git+rev-parse+HEAD|code-block|syntax|javascript|4095881|或|4095882|git+rev-parse+--verify+HEAD|4095883|您还可以检索简短版本，如下所示|4095884|git+rev-parse+--short+HEAD|4095885|Sidenote:如果你想把引用(分支和标签)转换成-1，有git+show-ref和git+for-each-ref。|offset|length|style|BOLD|CODE|4095886|entityMap^0|0|0|0|0|0|0|0|9|H|2|K|2|Q|Y|U|C|17|G|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|12|8|@]|9|@]|A|$E|F]]|$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]|$Q|1C|R|1D|S|U]|$Q|1E|R|1F|S|U]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|W|$]]

To turn arbitrary extended object reference into SHA-1, use simply <a href="http://git-scm.com/docs/git-rev-parse" rel="noreferrer" title="git-rev-parse - Pick out and massage parameters">git-rev-parse</a>, for example
<pre><code>git rev-parse HEAD
</code></pre>
or
<pre><code>git rev-parse --verify HEAD
</code></pre>
You can also retrieve the short version like this
<pre><code>git rev-parse --short HEAD
</code></pre>
Sidenote: If you want to turn references (branches and tags) into SHA-1, there is <code>git show-ref</code> and <code>git for-each-ref</code>.

blocks|key|4095932|text|git+describe也总是存在的。默认情况下，它会为您提供--|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4095933|john@eleanor:/dev/shm/mpd/ncmpc/pkg+(master)$+git+describe+--always
release-0.19-11-g7a68a75|code-block|syntax|javascript|4095934|entityMap^0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

There's always <code>git describe</code> as well. By default it gives you --

<pre><code>john@eleanor:/dev/shm/mpd/ncmpc/pkg (master)$ git describe --always
release-0.19-11-g7a68a75
</code></pre>

blocks|key|4095956|text|如果您只需要缩短的提交散列：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4095957|git+log+--pretty=format:'%25h'+-n+1|code-block|syntax|javascript|4095958|此外，使用%25H是获取长提交散列的另一种方式，可以简单地使用-1来代替-n+1。|offset|length|style|CODE|4095959|entityMap^0|0|0|5|2|T|2|Y|4|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|N|$]]

If you only want the shortened commit hash:
<pre><code>git log --pretty=format:'%h' -n 1
</code></pre>
Furthermore, using <code>%H</code> is another way to get the long commit hash, and simply <code>-1</code> can be used in place of <code>-n 1</code>.

blocks|key|2125|text|另一个，使用git日志：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2126|git+log+-1+--format="%25H"|code-block|syntax|javascript|2127|它非常类似于@outofculture，只是短了一点。|2128|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Another one, using git log:

<pre><code>git log -1 --format="%H"
</code></pre>

It's very similar to the of @outofculture though a bit shorter.

blocks|key|4096021|text|如果在脚本执行过程中需要将散列存储在变量中，则可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4096022|last_commit=$(git+rev-parse+HEAD);|code-block|syntax|javascript|4096023|或者，如果您只想要前10个字符(如github.com+)|4096024|last_commit=$(git+rev-parse+--short=10+HEAD);|4096025|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you need to store the hash in a variable during a script, you can use
<pre class="lang-sh prettyprint-override"><code>last_commit=$(git rev-parse HEAD);
</code></pre>
Or, if you only want the first 10 characters (like github.com does)
<pre class="lang-sh prettyprint-override"><code>last_commit=$(git rev-parse --short=10 HEAD);
</code></pre>

blocks|key|4096067|text|为了完整性，因为还没有人建议这样做。.git/refs/heads/master是一个只包含一行的文件：master上最近一次提交的散列。所以你可以直接从那里读到它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4096068|或者，如命令所示：|4096069|cat+.git/refs/heads/master|code-block|syntax|javascript|4096070|4096071|更新：|4096072|请注意，git现在支持将一些head+ref存储在pack-ref文件中，而不是作为文件存储在/+refs+/head/文件夹中。https://www.kernel.org/pub/software/scm/git/docs/git-pack-refs.html|4096073|entityMap|0|LINK|mutability|MUTABLE|url|https://www.kernel.org/pub/software/scm/git/docs/git-pack-refs.html^0|I|M|1G|6|0|0|0|0|0|1T|1V|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|17|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|R|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

For completeness, since no-one has suggested it yet. <code>.git/refs/heads/master</code> is a file that contains only one line: the hash of the latest commit on <code>master</code>. So you could just read it from there.

Or, as as command:

<pre><code>cat .git/refs/heads/master
</code></pre>

<hr>

Update:

Note that git now supports storing some head refs in the pack-ref file instead of as a file in the /refs/heads/ folder. <a href="https://www.kernel.org/pub/software/scm/git/docs/git-pack-refs.html">https://www.kernel.org/pub/software/scm/git/docs/git-pack-refs.html</a>

blocks|key|4096094|text|我所知道的最简洁的方式是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4096095|git+show+--pretty=%25h+|code-block|syntax|javascript|4096096|如果您想要散列的特定位数，可以添加：|4096097|--abbrev=n|4096098|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The most succinct way I know:

<pre><code>git show --pretty=%h 
</code></pre>

If you want a specific number of digits of the hash you can add:

<pre><code>--abbrev=n
</code></pre>

blocks|key|878092|text|git+show-ref+--head+--hash+head|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|878093|如果你想提高速度，the+approach+mentioned+by+Deestan|unstyled|offset|length|878094|cat+.git/refs/heads/<branch-name>|878095|比这里列出的任何其他方法都要快得多。|878096|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/12913817/72321^0|0|9|X|0|0|0|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|@$G|W|H|X|1|Y]]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$B|C]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|F|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

<pre><code>git show-ref --head --hash head
</code></pre>

If you're going for speed though, <a href="https://stackoverflow.com/a/12913817/72321">the approach mentioned by Deestan</a>

<pre><code>cat .git/refs/heads/&lt;branch-name&gt;
</code></pre>

is significantly faster than any other method listed here so far.

blocks|key|2240|text|也许你想要一个别名，这样你就不必记住所有漂亮的细节了。执行以下步骤之一后，您将能够简单地键入：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2241|$+git+lastcommit
49c03fc679ab11534e1b4b35687b1225c365c630|code-block|syntax|javascript|2242|关于accepted+answer，这里有两种方法来设置它：|offset|length|2243|1)通过编辑全局配置来显式地教授git+(我最初的答案)：|2244|+#+open+the+git+config+editor
+$+git+config+--global+--edit
+#+in+the+alias+section,+add
+...
+[alias]
+++lastcommit+=+rev-parse+HEAD
+...|2245|2)或者如果你想要一个捷径来教git一个捷径，就像Adrien最近评论的那样：|2246|$+git+config+--global+alias.lastcommit+"rev-parse+HEAD"|2247|从现在开始，使用git+lastcommit来显示最后一次提交的散列。|style|CODE|2248|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/949391/890242^0|0|0|2|F|0|0|0|0|0|0|8|E|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@$I|17|J|18|1|19]]|A|$]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1E|8|@$I|1F|J|1G|U|V]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Perhaps you want an alias so you don't have to remember all the nifty details. After doing one of the below steps, you will be able to simply type:

<pre><code>$ git lastcommit
49c03fc679ab11534e1b4b35687b1225c365c630
</code></pre>

Following up on the <a href="https://stackoverflow.com/a/949391/890242">accepted answer</a>, here are two ways to set this up:

1) Teach git the explicit way by editing the global config (my original answer):

<pre><code> # open the git config editor
 $ git config --global --edit
 # in the alias section, add
 ...
 [alias]
 lastcommit = rev-parse HEAD
 ...
</code></pre>

2) Or if you like a shortcut to teach git a shortcut, as recently commented by Adrien:

<pre><code>$ git config --global alias.lastcommit "rev-parse HEAD"
</code></pre>

From here on, use <code>git lastcommit</code> to show the last commit's hash.

blocks|key|878258|text|如果你想用超级黑客的方式做到这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878259|cat+.git/`cat+.git/HEAD+%7C+cut+-d+\++-f+2`|code-block|syntax|javascript|878260|基本上，git将HEAD的位置存储在.git/HEAD中，格式为ref:+{path+from+.git}。这个命令读出它，切下"ref："，然后读出它所指向的任何文件。|offset|length|style|CODE|878261|当然，这在独立HEAD模式下会失败，因为HEAD不会是"ref:..."，而是散列本身-但你知道，我认为你的bash一行程序不会有那么多的智能。如果你不认为分号在作弊...|878262|HASH="ref:+HEAD";+while+[[+$HASH+==+ref\:*+]];+do+HASH="$(cat+".git/$(echo+$HASH+%7C+cut+-d+\++-f+2)")";+done;+echo+$HASH|878263|entityMap^0|0|0|W|L|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

If you want the super-hacky way to do it:

<pre><code>cat .git/`cat .git/HEAD | cut -d \ -f 2`
</code></pre>

Basically, git stores the location of HEAD in .git/HEAD, in the form <code>ref: {path from .git}</code>. This command reads that out, slices off the "ref: ", and reads out whatever file it pointed to.

This, of course, will fail in detached-head mode, as HEAD won't be "ref:...", but the hash itself - but you know, I don't think you expect that much smarts in your bash one-liners. If you don't think semicolons are cheating, though...

<pre><code>HASH="ref: HEAD"; while [[ $HASH == ref\:* ]]; do HASH="$(cat ".git/$(echo $HASH | cut -d \ -f 2)")"; done; echo $HASH
</code></pre>

blocks|key|878359|text|在您的主目录中的文件".gitconfig“中添加以下内容|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878360|[alias]
sha+=+rev-parse+HEAD|code-block|syntax|javascript|878361|然后，您将有一个更容易记住的命令：|878362|$+git+sha
59fbfdbadb43ad0b6154c982c997041e9e53b600|878363|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

in your home-dir in file ".gitconfig" add the following

<pre><code>[alias]
sha = rev-parse HEAD
</code></pre>

then you will have an easier command to remember: 

<pre><code>$ git sha
59fbfdbadb43ad0b6154c982c997041e9e53b600
</code></pre>

blocks|key|4096390|text|要获取完整SHA，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4096391|$+git+rev-parse+HEAD
cbf1b9a1be984a9f61b79a05f23b19f66d533537|code-block|syntax|javascript|4096392|要获取缩短版本，请执行以下操作：|4096393|$+git+rev-parse+--short+HEAD
cbf1b9a|4096394|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

To get the full SHA:

<pre><code>$ git rev-parse HEAD
cbf1b9a1be984a9f61b79a05f23b19f66d533537
</code></pre>

To get the shortened version:

<pre><code>$ git rev-parse --short HEAD
cbf1b9a
</code></pre>

blocks|key|878401|text|下面是另一个直接访问的实现：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878402|head="$(cat+".git/HEAD")"
while+[+"$head"+!=+"${head#ref:+}"+];+do
++head="$(cat+".git/${head#ref:+}")"
done|code-block|syntax|javascript|878403|这也适用于http，这对本地包归档很有用(我知道:对于公共网站，不建议将.git目录设为可访问)：|878404|head="$(curl+-s+"$baseurl/.git/HEAD")"
while+[+"$head"+!=+"${head#ref:+}"+];+do
++head="$(curl+-s+"$baseurl/.git/${head#ref:+}")"
done|878405|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here is another direct-access implementation:

<pre><code>head="$(cat ".git/HEAD")"
while [ "$head" != "${head#ref: }" ]; do
 head="$(cat ".git/${head#ref: }")"
done
</code></pre>

This also works over http which is useful for local package archives (I know: for public web sites it's not recommended to make the .git directory accessable):

<pre><code>head="$(curl -s "$baseurl/.git/HEAD")"
while [ "$head" != "${head#ref: }" ]; do
 head="$(curl -s "$baseurl/.git/${head#ref: }")"
done
</code></pre>

blocks|key|1302923|text|这是另一种方法，使用:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1302924|git+log+%7C+grep+-o+'\w\{8,\}'+%7C+head+-n+1|code-block|syntax|javascript|1302925|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|$]]

Here is another way of doing it with :)

<pre><code>git log | grep -o '\w\{8,\}' | head -n 1
</code></pre>

blocks|key|878440|text|提交哈希|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878441|git+show+-s+--format=%25H|code-block|syntax|javascript|878442|缩写提交散列|878443|git+show+-s+--format=%25h|878444|-s标志与--no-patch相同，代表“抑制差异输出”。|offset|length|style|CODE|878445|单击here查看更多git+show示例。|878446|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-show#_examples^0|0|0|0|0|0|2|5|A|0|A|8|2|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@$M|15|N|16|O|P]|$M|17|N|18|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@$M|1A|N|1B|O|P]]|9|@$M|1C|N|1D|1|1E]]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

Commit hash
<pre><code>git show -s --format=%H
</code></pre>
Abbreviated commit hash
<pre><code>git show -s --format=%h
</code></pre>
The <code>-s</code> flag is same as <code>--no-patch</code> and stands for &quot;Suppress diff output&quot;.
Click <a href="https://git-scm.com/docs/git-show#_examples" rel="noreferrer">here</a> for more <code>git show</code> examples.

blocks|key|878498|text|我需要一些更不同的东西:显示提交的完整sha1，但如果工作目录不干净，则在末尾附加一个星号。除非我想使用多个命令，否则前面答案中的所有选项都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878499|下面是一个可以做到这一点的liner：|878500|git+describe+--always+--abbrev=0+--match+"NOT+A+TAG"+--dirty="*"|offset|length|style|CODE|878501|结果：f5366ccb21588c0d7a5f7d9fa1d3f85e9f9d1ffe*|878502|说明:描述(使用带注释的标签)当前提交，但仅使用包含"NOT+A+TAG“的标签。由于标记不能包含空格，因此这永远不会与标记匹配，而且由于我们希望显示结果--always，因此该命令将返回显示提交的完整(--abbrev=0)+sha1，并且如果工作目录为--dirty，则会附加一个星号。|878503|如果您不想附加星号，此命令的工作方式与前面答案中的所有其他命令相同：|878504|git+describe+--always+--abbrev=0+--match+"NOT+A+TAG"|878505|结果：f5366ccb21588c0d7a5f7d9fa1d3f85e9f9d1ffe|878506|entityMap^0|0|0|0|1S|0|3|15|0|25|8|2U|A|3K|7|0|0|0|1G|0|3|14|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$F|14|G|15|H|I]|$F|16|G|17|H|I]|$F|18|G|19|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@$F|1C|G|1D|H|I]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1E|8|@$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|U|$]]

I needed something a little more different: display the full sha1 of the commit, but append an asterisk to the end if the working directory is not clean. Unless I wanted to use multiple commands, none of the options in the previous answers work.

Here is the one liner that does: 
<code>git describe --always --abbrev=0 --match "NOT A TAG" --dirty="*"</code> 
Result: <code>f5366ccb21588c0d7a5f7d9fa1d3f85e9f9d1ffe*</code>

Explanation: describes (using annotated tags) the current commit, but only with tags containing "NOT A TAG". Since tags cannot have spaces, this never matches a tag and since we want to show a result <code>--always</code>, the command falls back displaying the full (<code>--abbrev=0</code>) sha1 of the commit and it appends an asterisk if the working directory is <code>--dirty</code>.

If you don't want to append the asterisk, this works like all the other commands in the previous answers: 
<code>git describe --always --abbrev=0 --match "NOT A TAG"</code> 
Result: <code>f5366ccb21588c0d7a5f7d9fa1d3f85e9f9d1ffe</code>

blocks|key|2443|text|git+rev-parse+HEAD做到了这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2444|如果您需要将其存储到签出后，而不是保存实际分支(如果有)，则可能更可取：|2445|cat+.git/HEAD|code-block|syntax|javascript|2446|输出示例：|2447|ref:+refs/heads/master|2448|解析它：|2449|cat+.git/HEAD+%7C+sed+"s/%5E.\%2B+$.\%2B$$/\1/g"|2450|如果你使用Windows，那么你可以考虑使用wsl.exe：|2451|wsl+cat+.git/HEAD+%7C+wsl+sed+"s/%5E.\%2B+$.\%2B$$/\1/g"|2452|输出：|2453|refs/heads/master|2454|这个值可以在以后用于git签出，但它会指向它的SHA。要使其按名称指向实际的当前分支，请执行以下操作：|2455|wsl+cat+.git/HEAD+%7C+wsl+sed+"s/%5E.\%2B+$.\%2B$$/\1/g"+%7C+wsl+sed+"s/%5Erefs\///g"++%7C+wsl+sed+"s/%5Eheads\///g"|2456|2457|master|2458|entityMap^0|0|I|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1F|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1G|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1H|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1I|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1J|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1K|8|@]|D|@]|E|$]]|$1|W|3|X|5|J|7|1L|8|@]|D|@]|E|$K|L]]|$1|Y|3|Z|5|6|7|1M|8|@]|D|@]|E|$]]|$1|10|3|11|5|J|7|1N|8|@]|D|@]|E|$K|L]]|$1|12|3|13|5|6|7|1O|8|@]|D|@]|E|$]]|$1|14|3|15|5|J|7|1P|8|@]|D|@]|E|$K|L]]|$1|16|3|Z|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|17|3|18|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|19|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|1A|$]]

<code>git rev-parse HEAD</code> does the trick.
If you need to store it to checkout back later than saving actual branch if any may be preferable:
<pre class="lang-sh prettyprint-override"><code>cat .git/HEAD
</code></pre>
Example output:
<pre><code>ref: refs/heads/master
</code></pre>
Parse it:
<pre class="lang-sh prettyprint-override"><code>cat .git/HEAD | sed &quot;s/^.\+ $.\+$$/\1/g&quot;
</code></pre>
If you have Windows then you may consider using wsl.exe:
<pre><code>wsl cat .git/HEAD | wsl sed &quot;s/^.\+ $.\+$$/\1/g&quot;
</code></pre>
Output:
<pre><code>refs/heads/master
</code></pre>
This value may be used to git checkout later but it becomes pointing to its SHA. To make it to point to the actual current branch by its name do:
<pre><code>wsl cat .git/HEAD | wsl sed &quot;s/^.\+ $.\+$$/\1/g&quot; | wsl sed &quot;s/^refs\///g&quot; | wsl sed &quot;s/^heads\///g&quot;
</code></pre>
Output:
<pre><code>master
</code></pre>

blocks|key|878552|text|在git+bash上，只需运行$+git+log+-1|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878553|您将看到，命令后面的这些行。|878554|commit+d25c95d88a5e8b7e15ba6c925a1631a5357095db+..+(info+about+your+head)

d25c95d88a5e8b7e15ba6c925a1631a5357095db,+is+your+SHA+for+last+commit.|code-block|syntax|javascript|878555|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

On git bash, simply run
$ git log -1

you will see, these lines following your command.

<pre><code>commit d25c95d88a5e8b7e15ba6c925a1631a5357095db .. (info about your head)

d25c95d88a5e8b7e15ba6c925a1631a5357095db, is your SHA for last commit.
</code></pre>

blocks|key|1303045|text|echo“正在打印当前分支的上次提交id#：”；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1303046|+git+reflog|code-block|syntax|javascript|1303047|​|1303048|📷|atomic|offset|length|1303049|1303050|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e9d823980feb6d58a87336edb681d94a.jpeg|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|10|8|@]|9|@$L|11|M|12|1|13]]|A|$]]|$1|N|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V|W|-4]]]]

echo &quot;printing last commit id# for current branch:&quot;;
<pre><code> git reflog
</code></pre>
<a href="https://i.stack.imgur.com/B1t2F.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/B1t2F.jpg" alt="Image to show actul results" /></a>

blocks|key|4096823|text|主要的git代码库和子模块的漂亮打印：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4096824|echo+"Main+GIT+repo:"
echo+$(git+show+-s+--format=%25H)+'(main)'
echo+"Sub-modules:"
git+submodule+status+%7C+awk+'{print+$1,$2}'|code-block|syntax|javascript|4096825|输出示例：|4096826|3a032b0992d7786b00a8822bbcbf192326160cf9+(main)
7de695d58f427c0887b094271ba1ae77a439084f+sub-module-1
58f427c0887b01ba1ae77a439084947de695d27f+sub-module-2
d58f427c0887de6957b09439084f4271ba1ae77a+sub-module-3|4096827|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Pretty print of main git repo, and sub-modules:
<pre><code>echo &quot;Main GIT repo:&quot;
echo $(git show -s --format=%H) '(main)'
echo &quot;Sub-modules:&quot;
git submodule status | awk '{print $1,$2}'
</code></pre>
Example output:
<pre><code>3a032b0992d7786b00a8822bbcbf192326160cf9 (main)
7de695d58f427c0887b094271ba1ae77a439084f sub-module-1
58f427c0887b01ba1ae77a439084947de695d27f sub-module-2
d58f427c0887de6957b09439084f4271ba1ae77a sub-module-3
</code></pre>

I would like to retain (for now) the ability to link Git changesets to workitems stored in TFS.
I already wrote a tool (using a hook from Git) in which I can inject workitem identifiers into the message of a Git changeset.
I would also like to store the hash of the Git commit in a custom TFS workitem field. This way I can examine a workitem in TFS and see what Git changesets are associated with the workitem.
How can I easily retrieve the hash from the current commit from Git?

How to retrieve the hash for the current commit in Git?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我希望(目前)保留将Git变更集链接到存储在TFS中的工作项的能力。我已经编写了一个工具(使用来自Git的钩子)，可以在其中将工作项标识符注入到Git变更集的消息中。我还想将Git提交的散列存储在自定义的TFS工作项字段中。这样，我就可以在TFS中检查工作项，并查看与该工作项关联的Git变更集。如何才能轻松地从Git的...

问如何在Git中检索当前提交的哈希？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Git中检索当前提交的哈希？EN