···28282929## the diff soup model
30303131-When you create a PR on traditional code-forges (GitHub
3131+When you create a PR on traditional code forges (GitHub
3232specifically), the UX implicitly encourages you to address
3333your code review by *adding commits* on top of your original
3434set of changes:
···3737 suggestion into your PR
3838- GitHub only shows you the diff of all files at once by
3939 default
4040-- It is difficult to know what changed across force-pushes
4040+- It is difficult to know what changed across force pushes
41414242Consider a hypothetical PR that adds 3 commits:
4343···9696could do this with git if you are familiar with fixup
9797commits or interactive rebasing).
98989999-Lets try that again:
9999+Let's try that again:
100100101101```
102102[c] implement new feature across the board (HEAD)
···161161162162## interdiff code review on tangled
163163164164-To really explain how this works, lets start with a [new
164164+To really explain how this works, let's start with a [new
165165codebase](https://tangled.sh/@oppi.li/stacking-demo/):
166166167167```
···249249├ my set: introduce basic set operations
250250~
251251252252-# lets edit the implementation of `Union`
252252+# let's edit the implementation of `Union`
253253$ jj edit mk
254254255255# hack, hack, hack
···268268> there is a logic bug here, the condition should be negated.
269269270270```
271271-# lets edit the implementation of `Difference`
271271+# let's edit the implementation of `Difference`
272272$ jj edit so
273273274274# hack, hack, hack
···358358```
359359360360This feature writes `change-id` headers directly into the
361361-git commit object, and is visible to code-forges upon push,
361361+git commit object, and is visible to code forges upon push,
362362and allows you to stack your PRs on Tangled.
363363-364364-