Git uses the following information to generate the sha-1: The source tree of the commit (which unravels to all the subtrees and blobs) The parent commit sha1 The author info (with timestamp) The committer info (right, those are different!, also with timestamp) The commit message (on the complete explanation; look here). Git does NOT guarantee … Read more
Figuring out if something is a merge is easy. That’s all commits with more than one parent. To check for that, you can do, for example $ git cat-file -p $commit_id If there’s more than one `parent’ line in the output, you found a merge. For reverts it’s not as easy. Generally reverts are just … Read more
Git prefixes the object with “blob “, followed by the length (as a human-readable integer), followed by a NUL character $ echo -e ‘blob 14\0Hello, World!’ | shasum 8ab686eafeb1f44702738c8b0f24f2567c36da6d Source: http://alblue.bandlem.com/2011/08/git-tip-of-week-objects.html
No need to hack around getting data from the git command yourself. GitPython is a very nice way to do this and a lot of other git stuff. It even has “best effort” support for Windows. After pip install gitpython you can do import git repo = git.Repo(search_parent_directories=True) sha = repo.head.object.hexsha Something to consider when … Read more
To turn any extended object reference into a hash, use git-rev-parse: git rev-parse HEAD or git rev-parse –verify HEAD To retrieve the short hash: git rev-parse –short HEAD To turn references (e.g. branches and tags) into hashes, use git show-ref and git for-each-ref.