docs: describe the conflict-resolution workflow without open commits

This commit is contained in:
Martin von Zweigbergk 2022-11-04 18:02:35 -07:00 committed by Martin von Zweigbergk
parent 6dd91cf1c1
commit c8c4497ea0

View file

@ -53,15 +53,14 @@ markers by the resolved text. You don't need to resolve all conflicts at once.
You can even resolve part of a conflict by updating the different parts of the You can even resolve part of a conflict by updating the different parts of the
conflict marker. conflict marker.
If the commit with conflicts was closed, your conflict resolution would be in To resolve conflicts in a commit, use `jj new <commit>` to create a working-copy
the working-copy commit. Once you have resolved the conflicts, you would then commit on top. You would then have the same conflicts in the working-copy
typically use `jj squash` to move the conflict resolutions into the conflicted commit. Once you have resolved the conflicts, you can inspect the conflict
commit. resolutions with `jj diff`. Then run `jj squash` to move the conflict
resolutions into the conflicted commit. Alternatively, you can edit the commit
If the commit with conflicts was open, it would simply not have conflicts with conflicts directly in the working copy by using `jj edit <commit>`. The
anymore once you have resolved them. If you prefer to do the conflict resolution main disadvantage of that is that it's harder to inspect the conflict
in a separate commit, you can use `jj new` before you resolve the conflicts and resolutions.
then `jj squash` once you're done.
There's not yet a way of resolving conflicts in an external merge tool There's not yet a way of resolving conflicts in an external merge tool
(https://github.com/martinvonz/jj/issues/18). There's also no good way of (https://github.com/martinvonz/jj/issues/18). There's also no good way of