Difference between revisions of "Git fork"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | In [Git (software)|Git]], a '''fork''' is a copy of the [[Git repository]] associated with your ID. | + | In [[Git (software)|Git]], a '''fork''' is a copy of the [[Git repository]] associated with your ID. |
(TO DO: expand, organize, cross-reference, illustrate.) | (TO DO: expand, organize, cross-reference, illustrate.) | ||
Revision as of 08:55, 9 October 2015
In Git, a fork is a copy of the Git repository associated with your ID.
(TO DO: expand, organize, cross-reference, illustrate.)
Description
Any changes made to the original repository will be reflected back to your forked repositories.
When you are ready to merge your changes into the original repository, create a Git pull request.
If your pull request is approved by the administrator of the original repository, then your changes will be committed/merged with the existing original code-base. Until then, your changes will be reflected only in the copy you forked.
Fork-and-pull model
The Fork & Pull Model lets anyone fork an existing repository and push changes to their personal fork without requiring access be granted to the source repository. The changes must then be pulled into the source repository by the project maintainer.
Note that after forking you can clone your repository (the one under your name) locally on your machine. Make changes in it and push it to your forked repository. However, to reflect your changes in the original repository your pull request must be approved.
Fork versus clone
...
See Git clone.
See also
- [Git (software)]]
External links
- What is the difference between Forking and Cloning on GitHub? @ Stack Overflow
- Git fork is git clone? @ Stack Overflow
- git clone vs fork
