vscode-gitlens VS vscode-git-graph

IntelliJ: https://www.jetbrains.com/help/idea/investigate-changes.html

VSCode:

https://marketplace.visualstudio.com/items?itemName=mhutchie...

or https://github.com/gitkraken/vscode-gitlens#commit-graph-

SourceTree: https://confluence.atlassian.com/sourcetreekb/viewing-log-hi...

Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!

Btw, today I want to speak about something different, I love git and I love terminal, but sometimes I love having the info visualised appealingly and get info about the source control quickly. I work with VsCode typically, so some months ago I tried to find a solution for this editor that resolves what was said before. After googling and some testing, the result of my search was: GitLens. Now, I want to show you how it works and how it can improve your routine. So don't waste time and let's jump in it!

GitLens extension chef's kiss

for GitLens https://gitlens.amod.io/

The better version is to have something like gitlens installed into your IDE and have it dynamically render those git comments.

https://github.com/Axosoft/vscode-gitlens#current-line-blame...

I learned the cli first, but I do use vscode's git integration for staging and committing. I also love gitlens's "commits by file / line" feature.

Hi. Vs code is pretty well integrated with git. There are built in git support and a couple other plugins. For example, the most popular git plugin for vs code is git lens. It also has powerful rebase editor (i guess, it is my favorite feature), which you can enable by following this guide. I personally realy enjoing Git Graph extension, which allow you to observe your git history in pretty similar to git kraken way. It also provide navigation facilities and some other useful features.

Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!

I'm a paying user of Fork, it's my favorite Git GUI, I love it.

However, it "only" supports macOS and Windows. I'm migrating to Linux for my work and home computers, so I haven't used it in a while, just so I can get familiar with other tools available on Linux - and, importantly, learning to do more advanced Git operations in the terminal.

So far I still depend on a GUI, mainly VS Code's built-in Git integration and GitGraph.

https://github.com/mhutchie/vscode-git-graph

Also looking at GitLens: https://www.gitkraken.com/gitlens

..But I sure miss using Fork. I used it everyday for the last couple years. It does everything I want to do with Git, the UI is familiar and well-designed.

I see the main developer @DanPristupov is on HN, maybe he'd consider supporting Linux? I fully understand if you don't, since creating the same application for two OSes must be quite difficult already, especially for a small team rather than a company.

Probably the most underrated software I use daily are some of my Firefox extensions.

https://github.com/einaregilsson/Redirector redirects my YouTube, Google, Twitter and Reddit links to privacy friendly frontends (i.e. Invidious, Startpage, Nitter and Libreddit).

https://github.com/proginosko/LeechBlockNG helps me staying away from time sinks on the internet during the day.

On the development side I use...

https://github.com/aaronvegh/nsregextester as my tried and true tool for regex debugging.

https://github.com/mhutchie/vscode-git-graph is a marvelous Git GUI for VSCode.

VS Code does not appear to provide a stylesheet or anything to help you get off the ground, AFAICT… I wish they did. Every extension I know of has to implement basic components from scratch, styling and all. Seems like a lot of boilerplate is necessary before you can start developing anything the user will see on screen.