logoalt Hacker News

conradludgatetoday at 5:59 PM1 replyview on HN

My understanding of the way this is presented is that merges don't _block_ the workflow. In git, a merge conflict is a failure to merge, but in this idea a merge conflict is still present but the merge still succeeds. You can commit with conflicts unresolved. This allows you to defer conflict resolution to later. I believe jj does this as well?

Technically you could include conflict markers in your commits but I don't think people like that very much


Replies

rightbytetoday at 6:03 PM

> You can commit with conflicts unresolved.

True but it is not valid syntax. Like, you mean with the conflict lines?

show 3 replies