I get all excited when I load up Github's front-page and see something like:
"robyn has forked skx/xxx to robyn/xxx"
I wonder what they will do, what changes do they have in mind?
Days pass, and no commits happen.
Anti-social coding: Cloning the code, I guess in case I delete my repository, but not intending to make any changes.
Tags: github 9 comments
Well, `fork` is simply GitHub's on-site `clone`.
If you think about it, people clone repositories all the time - having a copy in case someone deletes the repository being one of the reasons.
In a non-GitHub workflow you'd normally get a `patch` emailed to you instead of a `pull request`. How many do people usually get? I suppose the ratio of GitHub's `pull requests` might be slightly higher than non-GitHub `patches` but not by a huge margin.
The upside of a `fork` as a "backup", is that one does need to `clone` any data locally.
Other than than that, there's not much of a difference me thinks.