Monorepo for Tangled forked from tangled.org/core
core blog posts stacking.md
11 kB · 351 lines
Markdown

--- atroot: true template: slug: stacking title: Jujutsu on Tangled subtitle: Tangled now supports jujutsu change-ids! date: 2025-06-02 image: https://assets.tangled.network/blog/interdiff_difference.jpeg authors: - name: Akshay email: akshay@tangled.sh handle: oppi.li draft: false --- Jujutsu is built around structuring your work into meaningful commits. Naturally, during code-review, you'd expect reviewers to be able to comment on individual commits, and also see the evolution of a commit over time, as reviews are addressed. We set out to natively support this model of code-review on Tangled. Tangled is a new social-enabled Git collaboration platform, [read our intro](/intro) for more about the project. For starters, I would like to contrast the two schools of code-review, the "diff-soup" model and the interdiff model. ## the diff-soup model When you create a PR on traditional code forges (GitHub specifically), the UX implicitly encourages you to address your code review by *adding commits* on top of your original set of changes: - GitHub's "Apply Suggestion" button directly commits the suggestion into your PR - GitHub only shows you the diff of all files at once by default - It is difficult to know what changed across force pushes Consider a hypothetical PR that adds 3 commits: ``` [c] implement new feature across the board (HEAD) | [b] introduce new feature | [a] some small refactor ``` And when only newly added commits are easy to review, this is what ends up happening: ``` [f] formatting & linting (HEAD) | [e] update name of new feature | [d] fix bug in refactor | [c] implement new feature across the board | [b] introduce new feature | [a] some small refactor ``` It is impossible to tell what addresses what at a glance, there is an implicit relation between each change: ``` [f] formatting & linting | [e] update name of new feature -------------. | | [d] fix bug in refactor -----------. | | |…