By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I've added a new setting git-graph.openDiffTabLocation to choose which pane the Visual Studio Code Diff opens in. Currently the Visual Studio Code API doesn't allow the Diff view to be opened below the active pane (when they add support for this I can add it as an option then), but they do allow support for opening it beside the active pane. For now the options are Active & Beside . I found that Beside works really nicely if the user uses the non Side-By-Side VSCode Diff. The setting defaults to the Active pane.

This will be available in 1.6.0, which will be release within the next day.

Just tried, working like charm. MANY THANKS AGAIN!!! This is definitely gonna boost my performance today.

I think this is the BEST Git Graph tool I ever used, and to be honest, I used to contribute to GNOME gitg to improve the graph chart, but this VScode extension just feels right, exactly a developer would ever want.

GREAT WORK!!!

Very nice setting, thanks!
Does the vscode API allows it to change the size of the split view when opening a new?
If I set "git-graph.openDiffTabLocation" to "Beside" it opens the diff view in a second view with the same width as the first. But this view is already splitted so a width of 2/3 would be nice. So all views then would have the same width.

Hi @hansunzner-kt,

I'll gather some feedback from other users around your suggestion to split the functionality of git-graph.openNewTabEditorGroup into individual settings, to see how much user interest there is for it. If there's enough interest and perceived value, I'll raise it as a new feature request.

FYI: While I've deliberately made the extension extremely configurable for users, the more settings I add, the harder it is for users to find a setting they're interested in within the Visual Studio Code Settings Editor. I already get many feature requests from users for functionality that is already available in an extension setting that they didn't find. Git Graph currently has 79 extension settings. Going forward, I have to balance the value added by new settings, with the loss of value from existing settings that become less discoverable.

I'll gather some feedback from other users around your suggestion to split the functionality of git-graph.openNewTabEditorGroup into individual settings, to see how much user interest there is for it. If there's enough interest and perceived value, I'll raise it as a new feature request.

Did you get some feedback yet?