Changes between Version 16 and Version 17 of versionControl/git


Ignore:
Timestamp:
Jan 24, 2017 9:48:58 AM (5 years ago)
Author:
juaco
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • versionControl/git

    v16 v17  
    579579== Fork a Repo ==
    580580
    581 A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.
     581A fork is a copy of a repository **under your own `GitHub` ID**. Forking a repository allows you to freely experiment with changes without affecting the original project. Forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.
     582
     583The main point to note here is that any changes made to the original repository will be reflected back to your forked repositories(you need to `fetch` and `rebase`). However, if you make any changes to your forked repository you will have to explicitly create a pull request to the original repository. 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.
    582584
    583585=== Fork an example repository ===