Open belonesox opened 6 years ago
Hi!
This sounds like an interesting case. The answer to the question depends a lot on how you want to use it. If you just want normal git functionality, but able to resolve merge conflicts from the UI, I would:
git add <path>
and git commit
to mark the conflicts as resolved.@jupyterlab/git
. It is still missing push/pull functionality, but hopefully it will get there. It should at least have the add/commit functionality.@jupyterlab/git
so that nbdime is a "diff provider". It would be possible to extend this work to have nbdime be a "merge tool provider" as well.If what you are looking for is simply merging three files (outside of git), there are other options as well.
@belonesox Would you consider this issue as resolved? Do you have any suggestions for changes to the documentation for the future (e.g. based on what I talked about in the previous comment)?
Sorry for delaying answers!
Install/enable the nbdime merge driver. After any actions that cause a merge conflict, the notebook will contain conflict markers. Open the notebook for editing, and resolve any conflicts as indicated by the markers.
Yes, already done it.
But wish to get better usability for newbies:
Is "Case 2" too complex to be easily implemented?
Case 2 is not super complex, but there is some wiring that needs to go into it. Where would you expect the button to be, and how should it work (how does it know which notebooks need merging?).
Hello.
Please, if it possible, provide me link to right docs/code/samples.