git-fork

Is there a way to hard-link all the duplicate objects in a folder containing multiple Git repositories? Explanation: I am hosting a Git server on my company server (Linux machine). The idea is to have a main canonical repository, to which every user doesn't have push access to, but every user forks the canonical repository (clones the canonical to the user's home directory, thereby creating hard-links actually). /canonical/Repo /Dev1/Repo (objects Hard-linked to /canonical/Repo to when initially cloned) /Dev2/Repo (objects Hard-linked to /canonical/Repo to when initially cloned) This all works

Stash enables automatic fork syncing if selected: https://confluence.atlassian.com/display/STASH/Keeping+forks+synchronized It will update any branches in your fork that you haven't modified. I've been unable to find similar automatic functionality in gitHub; all google searches are turning up manual ways to sync forks via your local cache. You could define a webhook to listen to upstream (the original repo) changes, and update your fork. In June 2016, you now have the service backstroke.us which listens to those events for you. No need to write your own listener. See 1egoman/backstroke Create

I have a public repository on GitHub. I want to replicate/copy it and work on a new project based on this repository, but I don't want to affect how it is now. I tried forking it using the GitHub UI but it didn't do anything. I don't think you can fork your own repo. Clone it and push it to a new repo is good but you need to: git clone https://github.com/userName/Repo New_Repo cd New_Repo git remote set-url origin https://github.com/userName/New_Repo git remote add upstream https://github.com/userName/Repo git push origin master git push --all (see git push ) See the all process described at "

I currently have a private repository on github that I want to make public. However some of the initial commits contain information that I don't want to make public (hardcoded crentials, etc). What is the easiest route to make the latest commit public (I don't really need or want the previous commits in the public repository) without including some or all of the commit history? You can limit the depth of the history while cloning : --depth <depth> Create a shallow clone with a history truncated to the specified number of revisions. Use this if you want limited history, but still some. Use the