Try the new Commit Graph Feature Preview!

[d13]

We're excited to introduce the Commit Graph, a new ✨GitLens+ feature that is currently available as a preview in our Insiders release! The Commit Graph helps you easily visualize branch structure and commit history. Not only does it help you verify your changes, but also easily see changes made by others and when. It is freely available for local and public repos, while a paid account is required for use on private repos.

New Commit Graph

The quickest way to get started is to click the Commit Graph icon from the Source Control toolbar:

We'd love to hear your feedback! 🙏

We're excited to bring this to you and ready to answer any questions and make improvements where needed.

[KostaMadorsky]

Hi team, thanks for finally bringing the git graph to GitLens, was really missing it from GitKraken which I could not use on our huge repo due to serious performance issues.

Are you planning to add the ability to checkout a branch by double-clicking on it on the graph like in GitKraken?

[KostaMadorsky]

If you run git log --oneline --all --date-order in your terminal, how long does it take to start showing data?

It takes around 2 sec or less.

[eamodio]

@KostaMadorsky would you mind trying the latest GitLens Insiders edition? It should have significant performance improvements to the Graph

[KostaMadorsky]

@eamodio much more usable now! Thanks. Takes only 3 seconds to load first 500 commits and approximately the same to load more (200 increments).

Now it's even faster than the Git Graph extension that takes around 6 seconds to load.

[eamodio]

Sweet! So the almost "constant" time is because we are using --date-order (or --topo-order or author-date-order if you change the gitlens.graph.commitOrdering setting) all of which require sorting all of the commits in the repository before any results are returned. Unfortunately, we need that to ensure the graph with be displayed properly.

If you are using more recent versions of Git you can enable the commit-graph feature by running git commit-graph write --reachable or git commit-graph write --reachable --changed-paths (see https://git-scm.com/docs/git-commit-graph for more details) this should result in FAR more performant sorts, for example using the Linux repository using --date-order took around ~8s on my machine, and after generating a commit-graph it cut it down to ~1s.

I'm also trying to figure out if there is a way to pre-detect that a repository will likely take a long time to sort (though so far I haven't been able to find anything that doesn't also take a long time) so that we could ask for a larger number of commits -- to minimize the sorting cost. I may just have to do some after-the-fact timings (and maybe cache them for each respository) to optimize that.

[KostaMadorsky]

Changed the default settings to load 2000 commits first and then 1000 when paginating. Works great, pretty much the same 3 seconds or so.

[KostaMadorsky]

Would also be great to get the context menu on commits/branches on right mouse click.
E.g. Cherry pick, revert, drop, create a branch, merge, rebase, etc.

I can see that most of the options are available from the ... menu in the Commit details section on the left pane when you select a commit on the graph.

[sozelfist]

Would also be great to get the context menu on commits/branches on right mouse click. E.g. Cherry pick, revert, drop, create a branch, merge, rebase, etc.

I can see that most of the options are available from the ... menu in the Commit details section on the left pane when you select a commit on the graph.

I agree with you and hope the team will develop this in the future.

[legacy100]

This is really lovely... thank you GITHUB

[hakobpogh]

The graph is the only reason I've paid for the GitLens+ and was waiting for it too long. But now I'm not using it as it's hard to use without the context menu. So eager to see it.

[hakobpogh]

I will use it in beta if you have the context menu available.

[eamodio]

Check out the latest GitLens Insiders edition for many updates -- much better perf, rich commit search support, and context menus! Let us know what you think -- and we are still actively working on all of it.

You can install the GitLens insiders edition from here. FYI, you will also need the latest VS Code Insiders edition until VS Code 1.72 ships -- since that is required for our context menu support.

Please be sure to disable or uninstall the stable version of GitLens first.

[heartacker]

how to disable the icon， I do not need this， thanks

[Kritiqual]

@Josverl I found this from my settings.json after using the gitlens setting (notice the graph key):

  "gitlens.menus": {
    "editor": {
      "blame": false,
      "clipboard": true,
      "compare": false,
      "history": false,
      "remote": false
    },
    "editorGroup": {
      "blame": true,
      "compare": true
    },
    "editorTab": {
      "clipboard": true,
      "compare": false,
      "history": false,
      "remote": false
    },
    "explorer": {
      "clipboard": true,
      "compare": true,
      "history": false,
      "remote": true
    },
    "scm": {
      "graph": false,
      "authors": true
    },
    "scmRepositoryInline": {
      "graph": false
    },
    "scmRepository": {
      "authors": true,
      "graph": false
    },
    "scmGroupInline": {
      "stash": true
    },
    "scmGroup": {
      "compare": true,
      "openClose": true,
      "stash": true
    },
    "scmItemInline": {
      "stash": false
    },
    "scmItem": {
      "clipboard": true,
      "compare": true,
      "history": true,
      "remote": false,
      "stash": true
    }
  },

[DeveloperCron]

To hide the Icon you can just right-click on the bar and press GitLens Commit graph, (works on mac)

[aalvrz]

I have already switched graph to false under scm group and still the button won't go away. I don't understand why a premium feature that I don't have access to has to clutter my usual UX of my workspace. Bad feature rollout IMO 👎🏽

[eamodio]

@aalvrz See here: #2196 as they are fully controllable. And to be clear the Graph is fully accessible to all users (no account needed) for local and public repos -- only private repos require a paid account.

[carvemerson]

Hi, add this to your settings.json:

"gitlens.menus": { "scmRepositoryInline": { "graph": false, } },

[sozelfist]

Well, great work!

[robrechtme]

Looking good! I was wondering why it looks exactly like the GitKraken commit graph? Is this some shared (open source) code or is it rewritten from scratch?

[alexander-kastil]

Honestley speaking the exeperience you provide with you graph is poor. I learned that you are going to add features. But going out to public with less that free vs code extension like Git Graph offers for may years now is not a big thing https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph

[KostaMadorsky]

Why would you expect it to look anything other than Gitkraken? Gitlens was acquired by Gitkraken, you can even buy bundle Gitkraken + gitlens+.

[JustinGrote]

Not to dissuade this effort, however I'm going to need compelling reasons to pay for this when the excellent Git Graph extension is free...

[KostaMadorsky]

Git Graph has better performance with the huge repo I mentioned before.

The only thing that it does not have that gitlens one provides is integration with the left pane, so when you click something on in the graph, it will also scroll and open stuff on the left.

[wwarriner]

I appreciate the effort as well. Even if this feature were free, I still prefer Git Graph because it is less visually distracting for my poor, distractible brain. It's easier to scan and parse quickly, and is more compact. Something to consider as you develop the UX for this feature.

[eamodio]

@wwarriner Thanks for the feedback -- would love to hear more about what bits you find the most distracting.

[ShakedHad]

Hi, the graph view won't load for me, it just shows a blank page.
When hitting the reload button I receive this error: "Cannot write private member to an object whose class did not declare it".

GitLens version: 12.2.0
VSCode version: 1.70.2
Mac OS version: 12.5.1
Remote is hosted on private GitLab
GitLens+ licence

[TylerEich]

Same here! But it seems fixed on insiders using prerelease extension, so I'm not too concerned yet

[tryb3l]

Its fixed, just update your vscode to latest stable release 1.71

[d13]

This issue should be resolved with 12.2.1. Please update the extension and let us know if you have anymore issues.

[ShakedHad]

Works perfectly, thanks

[dylandifilippo]

Hello, thanks for this feature!

I signed up to have a 3 days free trial to GitLens+ but the commit graph is only working on a public repo. I cannot have it to work in my private repo from work.

What should I do ?

Have a nice day 😊

[tryb3l]

We're excited to introduce the Commit Graph, a new ✨GitLens+ feature that is currently available as a preview in our Insiders release! The Commit Graph helps you easily visualize branch structure and commit history. Not only does it help you verify your changes, but also easily see changes made by others and when. It is freely available for local and public repos, while a paid account is required for use on private repos.

New Commit Graph

The quickest way to get started is to click the Commit Graph icon from the Source Control toolbar:

We'd love to hear your feedback! 🙏

We're excited to bring this to you and ready to answer any questions and make improvements where needed.

I'd like to have a bit more vivid colors for a branches on the graph window.

[eamodio]

The colors on the graph are themeable -- and which can also be controlled via the workbench.colorCustomizations setting. See
https://code.visualstudio.com/api/references/theme-color for more details

And the graph colors are: gitlens.graphLane1Color - gitlens.graphLane10Color

[akshatmittal61]

Nice feature, thanks for bringing it to the Gitlens.

[asportnoy]

I do rebases with --committer-date-is-author-date (makes the commit dates not change) and that's really confusing the graph.

The commits boxed in red are meant to be on the main branch (leftmost) and the diverge near the top came off of the main branch, not the blue one. Pretty sure it worked correctly in the old version.

[asportnoy]

@eamodio

[ivancuric]

I am using Git Graph and it would be great if GitLens had the option to filter branches, including remote ones.

[eamodio]

You can right-click on any branch or tag and hide it from the Graph. And on remote branches there is an additional "Hide Remote" to hide all remote branches on that specific remote.

We will also be adding additional filtering options in the next couple of releases.

[ELLIOTTCABLE]

Definitely looking for the exact opposite of that, unfortunately — hiding individually isn't feasible with how many branches I check out and review; need an opt-in selection like the older Git Graph extension provides.

Excited to see where you take this, though!

[eamodio]

Yeah, we are planning to add an opt-in to what is shown on the Graph in addition to the current opt-out. Both opt-in and out will also be more configurable as well.

We will also be bringing the "solo" mode from the GitKraken Client as well to quickly show only a specific branch.

We'd definitely love to hear more about what you'd want to show/hide and how you'd like to configure it, etc.

[Eisenaxt]

You can right-click on any branch or tag and hide it from the Graph.

How do I make them visible again?

[eamodio]

See here: #2158 (reply in thread)

[begin-again]

Firstly I'm liking the graph, thanks for adding it to gitlens

suggestions

1. I wonder though if there were more possibilities for the auto-links, for instance to include the branch name with a regular expression. We use shortcut for our stories which suggests branch names with the story number embedded.
2. Could tags also be included?

[eamodio]

Can you provide more details on what you would like to see on your first point? Maybe open a separate feature request. As for tags, they should already be showing up, are you not seeing them or did you have something else in mind?

[begin-again]

for 1, we have branches that look like somebody/sc-123/a-story-name or sc-123/a-story-name where the 123 is the story identifier in shortcut.

2. I see the tags now. Doh!

[GeorgeLuizz]

Very good functionality.
I'm just wondering why the branch graph page is blurry, here's a picture of how it is.

[mikejmills]

Same thing, never saw a banner.

[d13]

I'll take a look into that. Are repos you're viewing private?

[mikejmills]

yes

[GeorgeLuizz]

It's a private repository. Being me and another author partner. It looks normal to him.

Vou dar uma olhada nisso. São repositórios que você está vendo privado?

[d13]

Thanks for the feedback! I have a fix in for this and should be included with our next release of GitLens Insiders edition.

[GriceTurrble]

Loving the graph view, been helping me a lot in combining loads of Dependabot branches into a smaller batch PR.

On that note, is it possible to get a link to PRs where the given branch is the source?

So, right between these two columns, if I'm looking at the head of a branch and that branch is the source for a PR (I'm interested mainly in open PRs, but there might be utility in showing closed ones, as well), it would be helpful to see another column that shows links to those PRs.

[eamodio]

I don't think PR are going to make it into this next release, but we will definitely be adding them right after that -- I definitely want that feature.

[ivancuric]

Would be great if you could filter out multiple branches manually instead of just current/all.

[crossan007]

Agree - I just bought the GitExtension Pro to see if I can centralize my workflow into VSCode; however, I need to be able to see the commit graph for multiple "specific" branches at the same time; so it looks like I'm staying with GitExtensions in a separate window for a while.

[crossan007]

It also seems like the "Commit Graph" is a singleton in the UI, so if I have multiple worktrees of a repository, I cannot simply open two GitLens Commit Graphs for two different branches

[eamodio]

Right now you can hide specific branches (or specific remotes) by right-clicking on the branch in the Graph, but we don't have the opposite only seen a few specific branches at this point.

Also today you can open 2 independent Graph's at the same time, but one needs to be in the bottom panel and one as an editor. We are thinking about allowing the opening of multiple Graph tabs at the same time, but have a couple more technical hurdles to make that happen.

[cryptoespanto68]

Nos complace presentar Commit Graph, un nuevo✨¡Función de GitLens+ que actualmente está disponible como vista previa en nuestro lanzamiento de Insiders! El gráfico de confirmación le ayuda a visualizar fácilmente la estructura de la rama y el historial de confirmación. No solo lo ayuda a verificar sus cambios, sino también a ver fácilmente los cambios realizados por otros y cuándo. Está disponible gratuitamente para repositorios locales y públicos, mientras que se requiere una cuenta paga para su uso en repositorios privados.

Nuevo gráfico de confirmación

La forma más rápida de comenzar es hacer clic en el icono Confirmar gráfico de la barra de herramientas de control de código fuente:

¡Nos encantaría escuchar sus comentarios! 🙏

Estamos emocionados de traerte esto y estamos listos para responder cualquier pregunta y hacer mejoras donde sea necesario.

[ivancuric]

How does the change search exactly work?

[Ryan-Zayne]

Why are all my repos being considered private by gitlens+?
I can't access the commit graph anymore!!

[Ryan-Zayne]

Yes it was working before 😥
And nothing changed with how I access the repo, I cloned it as usual only to discover that gitlens started seeing it and all my other subsequent repos as if there were private, hence preventing the use of gitlens+ features
HELP!😥

[eamodio]

@Ryan-Zayne Can you open a new issue for this and provide logs?

Please enable debug logging by running the GitLens: Enable Debug Logging command from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens & GitLens (Git) channels in the Output pane.

Once enabled, please reproduce the issue, and attach the logs from the GitLens channel, and if its Git related please also attach the logs from the GitLens (Git) channel.

Thank you!

[Ryan-Zayne]

Comment options

@Ryan-Zayne Can you open a new issue for this and provide logs?

Please enable debug logging by running the GitLens: Enable Debug Logging command from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens & GitLens (Git) channels in the Output pane.

Once enabled, please reproduce the issue, and attach the logs from the GitLens channel, and if its Git related please also attach the logs from the GitLens (Git) channel.

Thank you!

Thank you @eamodio cuz you just helped me solve the issue with your suggestion!😁
I open the gitlens debug (I never even l knew it was there) and I saw that gitlens kept failing to get the repo's info...
Then i pasted the log on google after fine tuning and I saw @d13 asking someone else if he had a proxy connection active as it may have been the cause of his issue with gitlens (different from mine)

Following which to test the solution, I then when back to vscode, searched for "proxy" on vscode settings, and turned off anything that popped up in that search and restarted vscode.
AND BAM!! Gitlens graph came back to normal!!!😁
Thanks once again!😁

[eamodio]

Glad it's fixed. Are you using a proxy? Or did you have one setup in vscode?

[Ryan-Zayne]

@eamodio to be sincere I actually don't even grasp the concept of "proxy" so I don't even know how the heck on works😅
But I guess http.proxy setting which is on by default in vscode, was the culprit here given the number of issues I've seen on vscode repo concerning it
Although I may be off with my speculation, but I'm just glad turning that off solved the issue 🧎

[Fish1]

Would it be possible to view all the changes that happen across multiple commits. Right now you can view all the changes from a single commit.

For example, on GitHub you can see all the changes that happened in a PR in a single commit.

Maybe being able to shift-select multiple commits?

[eamodio]

Unfortunately, not currently -- it is something we've talked about but hasn't made the roadmap yet. Great suggestion!

[pavlelee]

show current branch only is not work, click switch to another branch, have not any change, but branch is switch.

[pavlelee]

show current branch only is not work, click switch to another branch, have not any change, but branch is switch.

[muuvmuuv]

UI/UX question: can we have a third option for the detailed view inside the "Commit graph"-tab?

I don't like the right sidebar, even less when I am not working with the git history. It adds extra space. And the left is just too small. The way "Git graph" does it is perfect, it adds the information directly where I had clicked and therefore no need to move my eyes left↔right when I search something.

[psychedelicious]

The Gitlens fetch button has the same icon as the VSCode source control sync button, but they do different things.

Fetch does not pull or push changes. Sync does.

Fetch button:

Source control sync button (typically @ bottom-left corner of VSCode):

Also, the fetch icon and text are not aligned correctly.

[stuarthallows]

I've hidden a number of branches by right clicking the branch name in the graph and selecting Hide, but how do I now show those branches again?

[jkelroy]

@stuarthallows you can show them by selecting the eye icon at the top of the commit graph.

[hugocxl]

@d13 One of the best extensions for vscode by far. Thanks for the amazing work ❤️

[MadhavVij]

Is there a way to select multiple commits from graph to perform a collective action on all of them?
One of the use case would be to squash all the selected commits or look at the description of multiple commits at the same time.

[eamodio]

Not yet but it is something we are planning on adding. Just don't have an ETA just yet.

[MadhavVij]

Thanks for the update!

[YTingWu]

I hope to add the function of push tag.

[eamodio]

We will be adding that soon.

[YTingWu]

Thanks for the update!

[tbazant]

Hi, is there some explanation of what i actually see in the graph? it looks nice but i'm totally confused when looking at it. i would expect 'main' branch will be the straightest and other branches will depart and arrive at it later, but....i'm puzzled

which of these lines is the 'main' one?

[eamodio]

The purple dot that main is pointing to (3rd row down)

[lee1409]

Hi, I'm trying to open my submodule but somehow the graph will just show the graph of the main repo and I'm not sure why~ Anyone faces this problem?

[jkelroy]

Hi @lee1409, how are you opening up the commit graph for the submodule?

I am using the Show Commit Graph button in Source Control on my submodule and it is opening as expected. Does this work for you?

[lee1409]

Hi @jkelroy , sorry for the late reply.

So I tried to mock a abc repo that contains a submodule owne.

So when I clicked abc, it showed as expected, which was same as the git graph

But when I clicked owne, it still showed the same thing as abc.

git graph will show the log of owne repo.

Is this expected?

[jkelroy]

It looks like this is working as expected for me in the release version of GitLens but not in the pre-release. I wrote up an issue for that here.

If you are currently using the pre-release, if you switch to the release version (Extensions > settings > Switch to Release Version), are you able to open the submodule commit graph as expected?

[lee1409]

hi @jkelroy , I tried to reinstall the stable version and it works now. Thanks.

[rijk]

It would be nice to get the branch/tag as an inline pill if the column is hidden, like this: