Git log with graph of branches

[borekb]

GitLens is becoming my favorite Git GUI client, probably the only major feature that I still go to other clients is a visual log of the repository, incl. a graph of all branches.

GitKraken has a great branch visualization, IMO (image from their docs):

For VSCode, Git History extension but I generally prefer your approach of either using the quick pick UI or the sidebar. Having a tree graph in the sidebar would be greatly useful.

For reference, this Stack Overflow question lists a lot of graphical examples, incl. CLI (git log --graph).

[eamodio]

Unfortunately vscode won't allow anything but a tree in the sidebar currently, so any implementation would need to be in a editor tab (like Git History). While I would love to see this feature land, I don't envision getting to something like this anytime soon, but I would LOVE a PR 😉

[SheepDomination]

@borekb The screen capture you show is what I've been searching for in a VS Code extension for a while.

[th317erd]

Could this just be a live preview for now? This would work, allow the useful graph to be rendered, and when the support is added to VSCode (see here: microsoft/vscode#68266), could most likely easily be moved from a preview to the sidebar. Thoughts?

https://marketplace.visualstudio.com/items?itemName=hdg.live-html-previewer

[th317erd]

Also, I currently have zero time, but when my time does free up I would love to help with this feature. I will watch it closely to monitor progress and status, and input where I can be helpful

[SheepDomination]

It looks as if a graphical sidebar is possible ?

[stefanobartoletti]

Git Graph is another example of graphical visualization of branches and history (IMHO even better than Git History).

From what I see, it's a pretty new project, but I fin this extension easier and faster than other solutions.

[marcelhekking]

Git Graph is another example of graphical visualization of branches and history (IMHO even better than Git History).

From what I see, it's a pretty new project, but I fin this extension easier and faster than other solutions.

Thanx for the tip! Looks very good

[yunti]

Would be perfect if we could just merge git graph and git lens.

[zaboyle]

Is anyone working on something like this? I'd like to help contribute to creating a feature like this

[eamodio]

@zaboyle I'm not aware of anyone working on this. I'm working on a feature somewhat related (but different) -- a new Timeline view. You can see the code in the feature/timeline branch

@yunti if git graph or another extension does this well (I'm assuming) -- without GitLens duplicating that functionality is there a set of things to make the integration between the 2 better?

[borekb]

After a few months experience with Git Graph, I have to say that it works well and I use it besides GitLens, for different kinds of use cases.

Just to reiterate from the original feature request, I was wondering whether a graph-like UI could be integrated into GitLens' sidebar – instead of seeing a flat list, there would be "rails". But I'm not sure if that's possible or easy enough to implement. If not, that's fine, we now have Git Graph.

[ilanbiala]

It looks like webviews work in VS Code now (https://github.com/microsoft/vscode-extension-samples/tree/master/webview-view-sample)? Any update on adding a history graph to GitLens?

[eamodio]

This isn't something that I will likely add myself, but if the community wants to champion it and provide a PR (after discussing) I'm certainly open to it -- of course, depending on the complexity and scope of the changes required.

[whippingdot]

I know you said you wouldn't work on this, but I hope someone at least works on this feature. I really want this in my VS Code without having to install Git Graph. For now, I have git graph installed. The reason I want this to be in the GitLens extension is because I like having the number of extensions installed at a minimum (meaning below or equal to 20). Right now, I have twenty-one installed and so if Git Graph gets merged into GitLens I can reduce it to twenty.

[voxpelli]

@whippingdot Any specific reason why you want to keep your number of extensions to a minimum?

If the total code loaded is the same, then it doesn’t matter if it’s split between two extensions or is contained in a single one? So from a user perspective it shouldn’t really matter?

[whippingdot]

Really if I think about it, I realize it is because I don't want my computer filled with extensions from VS Code. The more extensions I download, the more space VS Code takes on my computer, right?

[farcaller]

The more features are there in the existing extensions the more space they take up too. But the extensions size is negligible as long as you have a node_modules somewhere on your disk.

[vadviktor]

What Git Graph and in general visual graphs help me with is that I can easily see where a feature branch diverges from master or how behind/ahead is it from master and/or other branches. I am a visual type of person.

Git Lens is huge, maybe I am missing this visual feedback feature, please correct me if something like this already exists.

[KostaMadorsky]

@eamodio do you know if there are any timelines on this feature?
From what I can see it's going to be a GitLens Plus paid feature.

Had to switch from GitKraken to GitLens for my current project, because GitKraken was way too slow (40 mil lines of code...).
And visual git graph is something I really miss, have to use another VS Code extension for it now.

[KostaMadorsky]

@vadviktor

Git Lens is huge, maybe I am missing this visual feedback feature, please correct me if something like this already exists.

This one is good enough:
https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph

Using it with GitLens, however, would be great to switch to a graph that is integrated into GitLens (e.g. clicking on commit in the commit list would navigate the graph).

[d13]

Released with v13.0.0

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.