- Compute the object ID without storing it:
git hash-object path/to/file
- Compute the object ID and store it in the Git database:
git hash-object -w path/to/file
- Compute the object ID specifying the object type:
git hash-object -t blob|commit|tag|tree path/to/file
- Compute the object ID from
cat path/to/file | git hash-object --stdin
git hash-object [-t <type>] [-w] [--path=<file> | --no-filters] [--stdin [--literally]] [--] <file>... git hash-object [-t <type>] [-w] --stdin-paths [--no-filters]
Computes the object ID value for an object with specified type with the contents of the named file (which can be outside of the work tree), and optionally writes the resulting object into the object database. Reports its object ID to its standard output. When <type> is not specified, it defaults to "blob".
- -t <type>
Specify the type of object to be created (default: "blob"). Possible values are commit, tree, blob, and tag.
Actually write the object into the object database.
Read the object from standard input instead of from a file.
Read file names from the standard input, one per line, instead of from the command-line.
Hash object as if it were located at the given path. The location of the file does not directly influence the hash value, but the path is used to determine which Git filters should be applied to the object before it can be placed in the object database. As a result of applying filters, the actual blob put into the object database may differ from the given file. This option is mainly useful for hashing temporary files located outside of the working directory or files read from stdin.
Hash the contents as is, ignoring any input filter that would have been chosen by the attributes mechanism, including the end-of-line conversion. If the file is read from standard input then this is always implied, unless the --path option is given.
Allow --stdin to hash any garbage into a loose object which might not otherwise pass standard object parsing or git-fsck checks. Useful for stress-testing Git itself or reproducing characteristics of corrupt or bogus objects encountered in the wild.
Part of the git(1) suite
git(1), git-merge-tree(1), git-mktag(1), git-replace(1).