Top all-time · #17102
Zac Bowling
Personal blog · zbowling.github.io/blogprogrammingsystems
Zac Bowling's personal blog at zbowling.github.io covers programming and systems. Since 2015, 4 different Hacker News readers have linked it 4 times, most often “GitHub forking has one big flaw (2011)”. The last post was in 2012, but the archive is still widely read.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog's 2011 post on problems with GitHub's fork feature. One commenter recalled it as fairly compelling, and another cited it as commentary on forking.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Zac Bowling's Code Labs - Open source projects, experiments, and technical writings
Most-linked posts?
- GitHub forking has one big flaw (2011)3 people · 3 mentions · first linked 2015-01-22
What Hacker News says?
Seems quite sensible. This, some commentary on forking[1] I ran across the other day, and the way SourceTree is miles beyond github's client, all make me suspect I should be at least trying out bitbucket. But since literally everything I collaborate with is on github, I've not gotten around to it. Am I missing out, or does bitbucket have its own weak spots? [1] http://zbowling.github.io/blog/2011/11/25/github/
Comment linking /blog/2011/11/25/github/
on “A better pull request”Submitted GitHub forking has one big flaw (2011) as a story · 76 points
HN discussionI read a blog post a few years back discussing some issues with Github's fork feature (as opposed to just creating a new repo that isn't explicitly linked to the original within Github's UI). From a quick search, I believe this[1] was it, and I remember finding it fairly compelling. [1]: https://zbowling.github.io/blog/2011/11/25/github/
Comment linking /blog/2011/11/25/github/
on “iOS on QEMU”Submitted GitHub forking has one big flaw (2011) as a story · 2 points
HN discussion