Re:2 out of 3 GitHub forks are completely empty
by dacort on Saturday April 09, 2011 @02:40PM
(#2427770)
Just because the repository is empty doesn't mean the forkers didn't modify the code. I've forked many a project, modified it locally, and not pushed it back up for a variety of reasons not limited to: laziness, abandonment, and shameful code that somebody would likely write a scornful blog post about. ;)
Re:2 out of 3 GitHub forks are completely empty
by tednaleid on Saturday April 09, 2011 @02:59PM
(#2427818)
I've done this too. Let's me create a github repo where "master" is fixed at a known version (to me) and I can clone it to any machine without worrying about remembering a the hash for the tag I want. I can push/pull at will and merge in changes from upstream whenever I desire. Sometimes local changes stay local, sometimes they get pushed out.
Github and Bitbucket aren't only for working on code with other people, they also let us consume projects at the rate that we want to consume them.
Re:2 out of 3 GitHub forks are completely empty
by indrekj on Saturday April 09, 2011 @03:24PM
(#2427878)
I usually clone the original repository. And after I make my changes, then I fork it and push to it. Most of the times there is no point to fork it before making changes.
Re:2 out of 3 GitHub forks are completely empty
by josegonzalez on Saturday April 09, 2011 @02:33PM
(#2427746)
Unfortunately, this "research" is flawed. If you pull in changes just right, the network view does not show the forks as branch off. I believe cherry-picking commits does this, and rebasing onto those commits may also do the same. Feel free to correct me, but that's been my personal experience.
Re:2 out of 3 GitHub forks are completely empty
by albertzeyer on Saturday April 09, 2011 @03:02PM
(#2427826)
The network view is not really intended to give a complete list of all contributors. It is intended to show the network of the different branches/forks. And it shows only a small time window (starting with the most recent time). So if there were commits earlier by other people and they were merged in, you will probably not see them.
I think under commits, the contributors list should be the requested information.
Re:2 out of 3 GitHub forks are completely empty
by josegonzalez on Saturday April 09, 2011 @03:45PM
(#2427931)
Thats not the same as you pulling in the commit in some way that obscures the contribution. I've done so on quite a few repositories (and I have enough repositories that all sorts of git nonsense has been tried). The big thing I try to conserve is attribution; I am not always the author of a changeset and I like to give credit where credit is due.
That said, you can also delete a commit from the Network view by issuing the command "git push -f". So no, I can't credibly say all your commits are listed, although I would hope you don't commit that unholy sin.
Github and Bitbucket aren't only for working on code with other people, they also let us consume projects at the rate that we want to consume them.
I think under commits, the contributors list should be the requested information.
https://github.com/cool-RR/GarlicSim/network
That said, you can also delete a commit from the Network view by issuing the command "git push -f". So no, I can't credibly say all your commits are listed, although I would hope you don't commit that unholy sin.
Fork it, commit something to your fork and I'll delete my repo.