如果你想要比哈希多一点的数据，你可以使用git-log:

import subprocess

def get_git_hash():
    return subprocess.check_output(['git', 'log', '-n', '1', '--pretty=tformat:%H']).strip()

def get_git_short_hash():
    return subprocess.check_output(['git', 'log', '-n', '1', '--pretty=tformat:%h']).strip()

def get_git_short_hash_and_commit_date():
    return subprocess.check_output(['git', 'log', '-n', '1', '--pretty=tformat:%h-%ad', '--date=short']).strip()

关于格式化选项的完整列表-查看git log——help

git describe命令是创建适合人类的代码“版本号”的好方法。参考文档中的例子:

和像少年犯一样的东西。git当前树，我得到: [torvalds@g5 git]$ git描述父 v1.0.4-14-g2414721 例如，我的“父”分支的当前头基于v1.0.4，但由于它在此之上有一些提交，describe在最后添加了额外提交的数量(“14”)和提交本身的缩写对象名称(“2414721”)。

在Python内部，你可以做如下的事情:

import subprocess
label = subprocess.check_output(["git", "describe"]).strip()

如果subprocess是不可移植的，并且你不想安装一个包来做这么简单的事情，你也可以这样做。

import pathlib

def get_git_revision(base_path):
    git_dir = pathlib.Path(base_path) / '.git'
    with (git_dir / 'HEAD').open('r') as head:
        ref = head.readline().split(' ')[-1].strip()

    with (git_dir / ref).open('r') as git_hash:
        return git_hash.readline().strip()

我只测试了这个在我的回购，但它似乎工作相当稳定。

我遇到了这个问题，并通过实现这个函数解决了它。 https://gist.github.com/NaelsonDouglas/9bc3bfa26deec7827cb87816cad88d59

from pathlib import Path

def get_commit(repo_path):
    git_folder = Path(repo_path,'.git')
    head_name = Path(git_folder, 'HEAD').read_text().split('\n')[0].split(' ')[-1]
    head_ref = Path(git_folder,head_name)
    commit = head_ref.read_text().replace('\n','')
    return commit


r = get_commit('PATH OF YOUR CLONED REPOSITORY')
print(r)

不需要自己从git命令中获取数据。GitPython是一种很好的方式来做到这一点，还有很多其他git的东西。它甚至有对Windows的“尽最大努力”支持。

在pip安装gitpython之后你就可以做了

import git
repo = git.Repo(search_parent_directories=True)
sha = repo.head.object.hexsha

使用这个库时需要考虑的一些问题。以下文件摘自gitpython.readthedocs.io

Leakage of System Resources GitPython is not suited for long-running processes (like daemons) as it tends to leak system resources. It was written in a time where destructors (as implemented in the __del__ method) still ran deterministically. In case you still want to use it in such a context, you will want to search the codebase for __del__ implementations and call these yourself when you see fit. Another way assure proper cleanup of resources is to factor out GitPython into a separate process which can be dropped periodically

如果您由于某些原因没有可用的Git，但您有Git repo(。)，你可以从. Git /fetch/heads/[branch]中获取提交哈希。

例如，我在存储库根运行了下面的Python代码片段来获得提交id:

git_head = '.git\\HEAD'

# Open .git\HEAD file:
with open(git_head, 'r') as git_head_file:
    # Contains e.g. ref: ref/heads/master if on "master"
    git_head_data = str(git_head_file.read())

# Open the correct file in .git\ref\heads\[branch]
git_head_ref = '.git\\%s' % git_head_data.split(' ')[1].replace('/', '\\').strip()

# Get the commit hash ([:7] used to get "--short")
with open(git_head_ref, 'r') as git_head_ref_file:
    commit_id = git_head_ref_file.read().strip()[:7]