It needs to be a bare repo because a not bare repo would have a working tree (meaning a specific version of that repo checked out and with files visible). Each time you are pushing to a non-bare repo, you have no guarantee that its working tree will reflect what you are pushing, since by … Read more
If your history is sane, you can take the commits out as patch and apply them in the new repository: cd repository git log –pretty=email –patch-with-stat –reverse –full-index –binary — path/to/file_or_folder > patch cd ../another_repository git am –committer-date-is-author-date < ../repository/patch Or in one line git log –pretty=email –patch-with-stat –reverse — path/to/file_or_folder | (cd /path/to/new_repository && … Read more
Another difference between a bare and non-bare repository is that a bare repository does not have a default remote origin repository: ~/Projects$ git clone –bare test bare Initialized empty Git repository in /home/derek/Projects/bare/ ~/Projects$ cd bare ~/Projects/bare$ git branch -a * master ~/Projects/bare$ cd .. ~/Projects$ git clone test non-bare Initialized empty Git repository in … Read more
Update Apr. 2021: there are a few tools created by the community that can do this for you: Download Directory (Credits to fregante) It has also been integrated into the excellent Refined Github chrome extension as a button in the Github web UI. GitZip (Credits to Kino – see his answer here) DownGit (Credits to … 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
1. You can’t spell The first thing to test is have you spelled the name of the package correctly? Package names are case sensitive in R. 2. You didn’t look in the right repository Next, you should check to see if the package is available. Type setRepositories() See also ?setRepositories. To see which repositories R … Read more
If you want to merge project-a into project-b: cd path/to/project-b git remote add project-a /path/to/project-a git fetch project-a –tags git merge –allow-unrelated-histories project-a/master # or whichever branch you want to merge git remote remove project-a Taken from: git merge different repositories? This method worked pretty well for me, it’s shorter and in my opinion a … 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
From the man file: When –cached is given, the staged content has to match either the tip of the branch or the file on disk, allowing the file to be removed from just the index. So, for a single file: git rm –cached mylogfile.log and for a single directory: git rm –cached -r mydirectory
How do I update or sync a forked repository on GitHub?