Provide way to open the merge editor even if the "source control" pane doesn't load about vscode HOT 5 OPEN

For reference, I see:

No merge editor button, none of the palette buttons do the thing I'm looking for.

from vscode.

Glad to hear you like the merge editor! ❤
I think you can configure VS Code as merge tool in git (there are CLI options to pass base/input1/input2/result paths to VS Code).
Then git merge tool (or a similar command) will open the merge editor of VS Code.

@lszomoru Can we do something here?

from vscode.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

from vscode.

@jakebailey, thanks for the screenshot. The "Source Control" view is being rendered by running git status and then parsing the output. Given the screenshot, what I am suspecting is that your are in a state in which running git status returns more than 10,000 entries hence we show a warning. Could you confirm that? Could you try setting the git.statusLimit setting to 0 in order to remove this limit. Did that help? Thanks!

Adding @chrmarti as well since he owns the merge conflict codelenses.

from vscode.

Setting "git.statusLimit": 0 allowed the source control page to load:

When opening a file manually in the editor, I now get the button bottom right:

And clicking on the conflicted file in the source control pane also works to open the merge editor.

Verifying without the setting, the source control page never loads and the button never appears, so my test case is at least good.

If you want to test this yourselves, I've pushed https://github.com/jakebailey/TypeScript/tree/merge-testing up; doing git merge main creates the 20000 file merge.

It sounds like I can leave this setting on; even when I set it to zero, the UI was responsive and working fine.

One thing I'm wondering here is whether or not it would be worth it for VS Code to instead use something like git diff --name-only --diff-filter=U or git diff --check to get a list of conflicting files, in the case where it can't parse out the status. But if setting the status limit to 0 to allow unlimited parsing works fine, that's also good and I'll keep using it in the meantime!

Offering the button on files with merge conflict markers would also be pretty helpful; that doesn't require any additional git parsing as VS Code already sees those markers and handles them for other UI...

from vscode.