I forked a git hub project on which I have to work on, what advantages will git hub fetch upstream provide because I can keep track on that project by updating it in separated folder, I feel its the easier way to do that!
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Collating my previous answers:
You would generally only clone a repo if you were a friend of the repo owner or had a suitable working relationship, (or they positively encourage it) so that when you push back a new branch of your work it would not cause any upset. This can avoid the branch bloat problem.
You would tend to fork a repo when you are interested in the work and want to try something out without having to get ‘permission’ first, which is one of the benefits of a DVCS system. The fork process also (automatically) provides you with a place of archive for your local work on the github server.
It will depend on your [project’s] workflow style e.g. git-scm.com/book/en/Distributed-Git-Distributed-Workflows or nvie.com/posts/a-successful-git-branching-model.
Using a fork allows you to prepare publicly a nice branch (commit series), and hold copies of all your WIP (work in progress) branches. As a personal fork, folk don’t expect all the branches to be polished – see how many forks have already been made of the repo you are interested in and have a look at their WIP to see a pattern (or anti-pattern;-)