Replies: 1 comment 3 replies
-
Possibly it should just link to the "conflicts" section of the "working copy" document, but I found that a little unclear as well, because it sort of glosses over the actual procedure for considering conflicts resolved:
I've noticed that in some of the documentation, such as the Git-comparison doc's command equivalence table, |
Beta Was this translation helpful? Give feedback.
-
The "First-class conflicts" document doesn't really give any clarity about what a user should do once they encounter a conflict. My current understanding is that the easiest and most common way to deal with conflicts is to configure a working merge-editor and then use
jj resolve
, but there may be other ways as well. It would be helpful if the page had a brief explanation of howresolve
works and/or just a link to the documentation forresolve
; and if there are other relevant commands thanjj resolve
, those should be mentioned as well.Beta Was this translation helpful? Give feedback.
All reactions