This repository is meant to provide an example for forking a repository on GitHub.
Creating a fork is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit Pull Requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub.
After forking this repository, you can make some changes to the project, and submit a Pull Request as practice.
For some more information on how to fork a repository, check out our guide, "Forking Projects"". Thanks! 💖
Fork, in the GitHub context, doesn't extend Git. It only allows clone on the server side.
When you clone a GitHub repo on your local workstation, you can only push changes to your own fork. You cannot contribute back to the upstream repo unless you are explicitly declared as "contributor". That's because your clone is a separate instance of that project.
If you want to contribute to the project, you can use forking to do it, in the following way:
- clone that GitHub repo on your GitHub account (that is the "fork" part, a clone on the server side)
- contribute commits to that GitHub repo (it is in your own GitHub account, so you have every right to push to it)
- signal any interesting contribution back to the original GitHub repo (that is the "pull request" part by way of the changes you made on your own GitHub repo)
If you want to keep a link with the original repo (also called upstream), you need to add a remote referring that original repo.
- Are git forks actually git clones?
- Git Command Line Cheat Sheets Comprehensive git command cheat sheets
- Git Magic A good introduction to git
- Pro Git Open source book about git.
- Collaborative GitHub Workflow