Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 53
    Along the lines of non-technical reasons: I've clicked on the 'fork' button several times hoping to see who's forked the repo, only to find that I've forked it. Ooops! Not sure if other's have done the same. Commented Jun 6, 2013 at 21:27
  • 70
    @gdw: Causing you to exclaim, "Oh, fork!" Commented Jun 7, 2013 at 0:47
  • 2
    I remember when I first learned about git and Github, I did some forking just because guides and tutorials seemed to propose it as the way to get your own copy of the code on your computer. Commented Jun 7, 2013 at 9:01
  • We use GitLab at work, so I know well the difference between clone and fork. I am also of the opinion that you don't need to fork if you don't want to issue a pull(merge for GitLab) request. Commented Nov 26, 2016 at 6:30
  • 4
    @Jesse, it's fine to do, but usually unnecessary in that case. A company might do it for code they depend on to make sure the original doesn't suddenly go away. If all you want to do is build from source, a clone is simpler. Commented Aug 4, 2017 at 1:25