Is there any way to retrieve only one specific commit from a remote Git repo without cloning it on my PC? The structure of remote repo is absolutely same as that of mine and hence there won't be any conflicts but I have no idea how to do this and I don't want to clone that huge repository.
I am new to git, is there any way?
Starting with Git version 2.5+ (Q2 2015), fetching a single commit (without cloning the full repo) is actually possible.
See commit 68ee628 by Fredrik Medley (
moroten), 21 May 2015.
(Merged by Junio C Hamano --
gitster -- in commit a9d3493, 01 Jun 2015)
You now have a new config (on the server side)
upload-packto accept a fetch request that asks for an object that is reachable from any ref tip. However, note that calculating object reachability is computationally expensive.
If you combine that server-side configuration with a shallow clone (
git fetch --depth=1), you can ask for a single commit (see
git fetch --depth=1 ../testrepo/.git $SHA1
You can use the
git cat-file command to see that the commit has been fetched:
git cat-file commit $SHA1
git upload-pack" that serves "
git fetch" can be told to serve commits that are not at the tip of any ref, as long as they are reachable from a ref, with
The full documentation is:
upload-pack: optionally allow fetching reachable sha1
uploadpack.allowReachableSHA1InWantconfiguration option set on the server side, "
git fetch" can make a request with a "want" line that names an object that has not been advertised (likely to have been obtained out of band or from a submodule pointer).
Only objects reachable from the branch tips, i.e. the union of advertised branches and branches hidden by
transfer.hideRefs, will be processed.
Note that there is an associated cost of having to walk back the history to check the reachability.
This feature can be used when obtaining the content of a certain commit, for which the sha1 is known, without the need of cloning the whole repository, especially if a shallow fetch is used.
Useful cases are e.g.
- repositories containing large files in the history,
- fetching only the needed data for a submodule checkout,
- when sharing a sha1 without telling which exact branch it belongs to and in Gerrit, if you think in terms of commits instead of change numbers.
(The Gerrit case has already been solved through
allowTipSHA1InWantas every Gerrit change has a ref.)
Git 2.6 (Q3 2015) will improve that model.
See commit 2bc31d1, commit cc118a6 (28 Jul 2015) by Jeff King (
(Merged by Junio C Hamano --
gitster -- in commit 824a0be, 19 Aug 2015)
refs: support negative
If you hide a hierarchy of refs using the
transfer.hideRefsconfig, there is no way to later override that config to "unhide" it.
This patch implements a "negative" hide which causes matches to immediately be marked as unhidden, even if another match would hide it.
We take care to apply the matches in reverse-order from how they are fed to us by the config machinery, as that lets our usual "last one wins" config precedence work (and entries in
.git/config, for example, will override
So you can now do:
git config --system transfer.hideRefs refs/secret git config transfer.hideRefs '!refs/secret/not-so-secret'
refs/secretin all repos, except for one public bit in one specific repo.
Git 2.7 (Nov/Dec 2015) will improve again:
See commit 948bfa2, commit 00b293e (05 Nov 2015), commit 78a766a, commit 92cab49, commit 92cab49, commit 92cab49 (03 Nov 2015), commit 00b293e, commit 00b293e (05 Nov 2015), and commit 92cab49, commit 92cab49, commit 92cab49, commit 92cab49 (03 Nov 2015) by Lukas Fleischer (
Helped-by: Eric Sunshine (
(Merged by Jeff King --
peff -- in commit dbba85e, 20 Nov 2015)
config.txt: document the semantics of
Right now, there is no clear definition of how
transfer.hideRefsshould behave when a namespace is set.
hideRefsprefixes match stripped names in that case. This is how
hideRefspatterns are currently handled in receive-pack.
hideRefs: add support for matching full refs
In addition to matching stripped refs, one can now add
hideRefspatterns that the full (unstripped) ref is matched against.
To distinguish between stripped and full matches, those new patterns must be prefixed with a circumflex (
Hence the new documentation:
If a namespace is in use, the namespace prefix is stripped from each reference before it is matched against
For example, if
refs/heads/masteris specified in
transfer.hideRefsand the current namespace is
refs/namespaces/foo/refs/heads/masteris omitted from the advertisements but
refs/namespaces/bar/refs/heads/masterare still advertised as so-called "have" lines.
In order to match refs before stripping, add a
^in front of the ref name. If you combine
!must be specified first.
R.. mentions in the comments the config
uploadpack.allowAnySHA1InWant, which allows
upload-pack to accept a
fetch request that asks for any object at all. (Defaults to
See commit f8edeaa (Nov. 2016, Git v2.11.1) by David "novalis" Turner (
upload-pack: optionally allow fetching any sha1
It seems a little silly to do a reachabilty check in the case where we trust the user to access absolutely everything in the repository.
Also, it's racy in a distributed system -- perhaps one server advertises a ref, but another has since had a force-push to that ref, and perhaps the two HTTP requests end up directed to these different servers.