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.

Merge Editor: "Accept All Changes from Left" command discoverability

See original GitHub issue

Testing #158819

I would love for the “Accept All Changes from …” command to be more discoverable as currently it is in the ... context menu. Have we ever considered lifting it as a primary action in the editor toolbar? Could we put a checkbox in the editor toolbar right before the “Input 1” label, and when that is clicked all changes from the side are accepted?

Issue Analytics

State:
Created a year ago
Comments:7 (7 by maintainers)

Top GitHub Comments

2reactions

hedietcommented, Sep 7, 2022

@daviddossett @isidorn

1reaction

isidorncommented, Sep 9, 2022

Shouldn’t the double check icon make sense here? ✔️ ✔️ Sort of like “take all”? Just an idea…

Top Results From Across the Web

Merge Editor: "Accept All Changes from Left" command ... - GitHub

Merge Editor : "Accept All Changes from Left" command discoverability Merge Editor: "Accept All Changes from Left" command discoverability.

How can I accept all current changes in VSCode at once?

Select all files in Merge Changes section. Choose Open File from right click menu.

Resolve merge conflicts | Bitbucket Cloud - Atlassian Support

A merge conflict is when Bitbucket Cloud can't automatically resolve differences in code between two commits.

November 2022 (version 1.74) - Visual Studio Code

Merge editor Undo/Redo - Quickly revert or reapply merge conflict actions. Manage unsafe repositories - Prevent Git operations on folders not owned by...

Resolve merge conflicts in Visual Studio - Microsoft Learn

If you need to keep all of your changes to a file, you can right-click it in the Unmerged Changes section and select...