-
Notifications
You must be signed in to change notification settings - Fork 59
Home
##Forking and cloning GitHub introduced to the world the concept of a ‘fork’, which is a personal copy of a GitHub hosted open source git repository . An important note: a ‘fork’ is a GitHub concept, not a git concept. Forks are implemented server-side in GitHub. A fork can only ever live on GitHub; in other words, you won’t ever have a fork on your hard drive.
A fork is created by browsing through GitHub hosted open source repositories, and clicking the fork button at the top. This creates a copy of the desired repository online, underneath your GitHub account. Typically, anonymous users have no permission to push changes into a GitHub repository, unless one is pushing to their own fork, which they implicitly own and always have push-pull permissions for. Forking serves as the starting activity to the method of contributing code on GitHub, ‘pull-requests’.
A developer can ‘clone’ any visible repository available GitHub. A clone is a copy of the particular git repository the developer has downloaded onto their own personal machine. An important note: a developer can clone any visible repository on GitHub, and they can clone their own forks of such projects. These are separate clones, and are distinguished by their different ‘origin’ URL’s
This repository follows the git flow workflow
- A gitflow extention has been developed to ease the use of the 'git flow' methodology, but requires manual installation by the user.