Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #12959

I

Isaac Corbrey

Personal blog · isaaccorbrey.com/ramblings · on HN as icorbreyprogrammingweb

Isaac Corbrey's personal blog at isaaccorbrey.com covers programming and web. Since 2026, 6 different Hacker News readers have linked it 6 times, most often “Jujutsu Megamerges for Fun and Profit”. It is still writing: the last post was on 2026-04-20, and you can follow it by feed.

Visit the blog
6mentions?
6HN people?
2026–2026first – last linked?

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

Linked posts about the Jujutsu (jj) 'megamerge' workflow, where in-progress workstreams are merged into one top-level commit. Commenters discuss it in the context of git history rules and VCS tooling.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

I like building tools, breaking workflows, and putting them back together better.

The author on HN?

icorbrey · 104 karma · member since 2024

Jujutsu sorcerer, whisperer of Rust, namer of things, cogitator of cognitives. https://isaaccorbrey.com

From their public HN profile, which links to this site.

Most-linked posts?

  1. Jujutsu Megamerges for Fun and Profit
    3 people · 3 mentions · first linked 2026-04-20

What Hacker News says?

  1. One of the golden rules of git is: Don't rewrite public history (for example by rebasing and force-pushing already published commits). The article hints at immutable and mutable commits ( https://isaaccorbrey.com/notes/jujutsu-megamerges-for-fun-an... ) but I am unsure about how fundamental this protection is. I don't want to ruin my co-worker's day by accidentally rewriting public history.

    Comment linking /notes/jujutsu-megamerges-for-fun-and-profit

    on “Jujutsu Megamerges for Fun and Profit”
  2. Submitted Jujutsu Megamerges for Fun and Profit as a story · 8 points

    HN discussion
  3. This remind me of [jj megamerge]( https://isaaccorbrey.com/notes/jujutsu-megamerges-for-fun-an... ). jj allows concentrating on developing while leaving things for vcs alone, as well as solving vcs things (conflicts) at very beginning (megamerge). Really good.

    Comment linking /notes/jujutsu-megamerges-for-fun-and-profit

    on “Defeating Git Rigour Fatigue with Jujutsu”
  4. Submitted Webrings as Collective OAuth as a story · 2 points

    HN discussion
  5. If you feel like fucking around with new source control tools, jj (jujutsu)'s megamerge workflow is really good at this. (If you're not interested, feel free to skip the rest of this). I have each in process workstream in a commit that is merged at the top level, then I have a new wip commit off of that where stuff I'm typing right now sits. It's easy to split/squash/absorb parts of that commit into the right destin…

    Comment linking /notes/jujutsu-megamerges-for-fun-and-profit

    on “Mercurial, 20 years and counting: how are we still alive and kicking? [video]”
  6. Submitted Jujutsu / jj megamerges for fun and profit as a story · 2 points

    HN discussion

Search all of HN for isaaccorbrey.com