Git This answer includes GitHub as many folks have asked about that too. Local repositories Git (locally) has a directory (.git) which you commit your files to and this is your ‘local repository’. This is different from systems like SVN where you add and commit to the remote repository immediately. Git stores each version of … Read more
The difference is that when using –mirror, all refs are copied as-is. This means everything: remote-tracking branches, notes, refs/originals/* (backups from filter-branch). The cloned repo has it all. It’s also set up so that a remote update will re-fetch everything from the origin (overwriting the copied refs). The idea is really to mirror the repository, … Read more
Note that Git 1.9/2.0 (Q1 2014) has removed that limitation. See commit 82fba2b, from Nguyễn Thái Ngọc Duy (pclouds): Now that git supports data transfer from or to a shallow clone, these limitations are not true anymore. The documentation now reads: –depth <depth>:: Create a ‘shallow’ clone with a history truncated to the specified number … Read more
Fork, in the GitHub context, doesn’t extend Git. It only allows clone on the server side. When you clone a GitHub repository on your local workstation, you cannot contribute back to the upstream repository unless you are explicitly declared as “contributor”. That’s because your clone is a separate instance of that project. If you want … Read more
A common cause is cloning using the default (HTTPS) instead of SSH. You can correct this by going to your repository, clicking “Clone or download”, then clicking the “Use SSH” button above the URL field and updating the URL of your origin remote like this: git remote set-url origin [email protected]:username/repo.git You can check if you … Read more
Note: the git1.7.10 (April 2012) actually allows you to clone only one branch: # clone only the remote primary HEAD (default: origin/master) git clone <url> –single-branch # as in: git clone <url> –branch <branch> –single-branch [<folder>] (<url> is the URL if the remote repository, and does not reference itself the branch cloned) You can see … Read more
What you are trying to do is called a sparse checkout, and that feature was added in git 1.7.0 (Feb. 2012). The steps to do a sparse clone are as follows: mkdir <repo> cd <repo> git init git remote add -f origin <url> This creates an empty repository with your remote, and fetches all objects … Read more
$ git clone will give you the whole repository. After the clone, you can list the tags with $ git tag -l and then checkout a specific tag: $ git checkout tags/<tag_name> Even better, checkout and create a branch (otherwise you will be on a branch named after the revision number of tag): $ git … Read more
Option A: git clone [email protected]:whatever folder-name Ergo, for right here use: git clone [email protected]:whatever . Option B: Move the .git folder, too. Note that the .git folder is hidden in most graphical file explorers, so be sure to show hidden files. mv /where/it/is/right/now/* /where/I/want/it/ mv /where/it/is/right/now/.* /where/I/want/it/ The first line grabs all normal files, the … Read more
Message ‘src refspec master does not match any’ when pushing commits in Git