Two solutions (or rather workarounds) that come to mind are: Use shallow clone i.e. git clone –depth=1, then deepen this clone using git fetch –depth=N, with increasing N. You can use git fetch –unshallow (since 1.8.0.3) to download all remaining revisions. Ask somebody to bundle up to some tagged release (see git-bundle(1) manpage). The bundle … Read more
You cannot provide options in the GIT_SSH environment variable; from the git man page: GIT_SSH If this environment variable is set then git fetch and git push will use this command instead of ssh when they need to connect to a remote system. The $GIT_SSH command will be given exactly two arguments: the username@host (or … Read more
TL;DR Given that you have an existing –depth 1 repository cloned from branch B and you’d like Git to act as if you removed and re-cloned, you can use this sequence of commands: git fetch –depth 1 git reset –hard origin/B git clean -dfx (e.g., git reset –hard origin/master—I cannot put italics in the code-literal … Read more
Append .wiki.git to the repository name. That is, if your repository name was foobar: git clone [email protected]:myusername/foobar.git would be the path to clone your repository and git clone [email protected]:myusername/foobar.wiki.git would be the path to clone its wiki. Note: You must have at least one page to be able to clone the wiki repo. (via @tobiasz-cudnik)
git clone –depth 1 –branch <tag_name> <repo_url> –depth 1 is optional but if you only need the state at that one revision, you probably want to skip downloading all the history up to that revision.
For the latest version of Bitbucket (2016+), the download link can be found in the Download menu item. Pre-2016 First method In the Overview page of the repo, there is a link to download the project. Second method Go to Downloads -> Branches -> Download the branch that you want (as .zip, .gz or .bz2). … Read more
This is the command that you need to execute on the mirror: git remote update
Beginning with Git 1.8.5, the server will send the actual branch name that HEAD points to, in the “symref” capability. If you have both a client and server newer than Git 1.8.5, it will update HEAD correctly. Prior to that, the client will guess what HEAD may have pointed to by comparing the object ID … Read more
This worked for me: git clone https://[email protected]/username/repo_name
A MingW update provide a new way to handle redirection with Git 2.15.x/2.16 (Q1 2018) See commit b2f5571, commit 1a172e4, commit 3f94442 (01 Nov 2017) by Johannes Schindelin (dscho). (Merged by Junio C Hamano — gitster — in commit 421f21c, 09 Nov 2017) mingw: add experimental feature to redirect standard handles Particularly when calling Git … Read more