Développer / Develop

Forking Workflow  : https://www.atlassian.com/git/workflows The Forking Workflow is fundamentally different than the other workflows discussed in this tutorial. Instead of using a single server-side repository to act as the “central” codebase, it gives every  developer a server-side repository. This means that each contributor has not one, but two Git repositories: a private local one and a public server-side one.  

git clone -b <branch> --branch <branch> --single-branch git://github/repository.git --[no-]single-branch Clone only the history leading to the tip of a single branch, either specified by the  --branch  option or the primary branch remote's  HEAD  points at. When creating a shallow clone with the  --depth option, this is the default, unless  --no-single-branch  is given to fetch the histories near the tips of all branches. Further fetches into the resulting repository will only update the remote-tracking branch for the branch this option was used for the initial cloning. If the HEAD at the remote did not point at any branch when  --single-branch  clone was made, no remote-tracking branch is created.