question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add "accept theirs", "accept ours" git commands/context menu actions

See original GitHub issue

I’m not sure how much this is due to me not being familiar with merging conflicts in vscode but I’m finding it next to impossible to use. For files with conflicts which vscode recognises (i.e. .py files) when I open the conflicted file it displays a bar at the top allow me to select the incoming changes or local changes. For all other files there doesn’t seem to be any way to accept / reject changes even at the file level (i.e. accept/reject all incoming changes)

i.e. I have an ipynb file with conflicts. Under MERGE CHANGES it has a C beside it. If I open the file it doesn’t present and options to diff or merge the files. I have nbdime installed but not sure how to configure it with vscode. But the issue also occurs for .log files etc.

If I right click on the files under MERGE CHANGES, there are options to ‘Accept All Current’ or ‘Accept All Incoming’. Neither of these appear to do anything, there’s no change to the indicators - the C icon is still displayed, and trying to stage continues to presents the warning “are you sure you want to stage xyz.ipynb with merge conflicts”

I’m having to resort to command line merging.

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

6reactions
joaomorenocommented, Jan 28, 2019

What we’re missing are context menu commands which “accept theirs” or “accept ours”. The current ones come from the git merge built-in extension and need to be removed.

0reactions
aleksandarboscommented, Mar 29, 2021

What’s the status on this one? Having a better way of handling binary file conflicts using VS code would be pretty handy.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Simple tool to 'accept theirs' or 'accept mine' on a whole file ...
The solution is very simple. git checkout <filename> tries to check out file from the index, and therefore fails on merge.
Read more >
Resolve conflicts with Ours or Theirs for file without opening diff
But sometimes I just want to use "Use all ours" or "Use all theirs" for one or more files. And now I have...
Read more >
Resolving Git Merge Conflicts in IntelliJ IDEA | Foojay.io Today
Another way of resolving conflicts is to right-click on the highlighted conflict in the central pane and use the commands from the context...
Read more >
Merge Conflicts — GitExtensions 3.4 documentation
Git Extensions will show warnings when there is a merge conflict in the status bar in the ... The context menu shows the...
Read more >
How to resolve a git merge conflict - Opensource.com
Git implements this feature by allowing multiple developers to work on a branch locally, then push their code to a central place. Then,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found