Vscode-gitlens Alternatives

Reviews and mentions

• The Myth of Self-Documenting Code
  1 project | news.ycombinator.com | 18 Oct 2021

  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...

• where add.
  1 project | reddit.com/r/ProgrammerHumor | 9 Oct 2021

  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.

• Replacing GitKraken
  2 projects | reddit.com/r/vscode | 30 Jul 2021

  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.

• Confused with fixing PR conflicts with VSCode
  1 project | reddit.com/r/git | 15 Jun 2021

  If you are going to use VSCode to manage your Git operations like merging, rebasing, etc., then I would highly recommend the GitLens plugin.

• GitHub and GitLens integration problems
  1 project | reddit.com/r/vscode | 31 May 2021

  Might be worth creating an issue ticket if you can't get it solved: https://github.com/eamodio/vscode-gitlens/issues

• Supercharge your git workflow with GitLens
  2 projects | dev.to | 21 May 2021

  Redder color means changes were made very recently in that area. Again you can fully customize age thresholds, locations, the color of the most recent and least recent changes, etc., from the settings.

  2 projects | dev.to | 21 May 2021

  So here are some of my favorite GitLens features that I use regularly. You can find the full list of the features here.

• Tips for Debugging Software like a Detective
  2 projects | dev.to | 15 May 2021

  Phone a friend. I recommend integrating git blame into your development environment I use the Git lens plugin which shows you, directly within files in a code editor, who authored certain file changes and the PR which can be helpful for quickly getting more context regarding decisions by looking at the associated Pull Request or having the opportunity to connect directly with the committer. Pair programming can be an effective way to debug and share knowledge. Similar, to the magic of figuring out the solution to a bug in the shower or overnight there is a phenomenon called rubber ducky debugging in which just explaining the issue to someone else (even an inanimate rubber duck) can help make the solution more obvious.

• Visualizar autor, fecha y commit en una revisión de código
  1 project | dev.to | 5 May 2021

  Enlace: https://gitlens.amod.io/ https://marketplace.visualstudio.com/items...

• Commits are snapshots, not diffs - The GitHub Blog
  3 projects | reddit.com/r/programming | 9 Apr 2021

  If you're using VS Code, get the GitLens extension. It has an interactive rebase editor which I find very helpful (as well as heaps of other nice features).

• Bullet point series - Part 2 - Some pretty sweet Visual Studio Extensions I Use
  2 projects | dev.to | 2 Apr 2021

  GitLens - https://gitlens.amod.io/#features , see who did what, when and why in your IDE and also quickly see any changes you have made

• Git's list of banned C functions
  9 projects | news.ycombinator.com | 4 Mar 2021

  I really wish tooling like this was more common:

  > Current Line Blame; Adds an unobtrusive, customizable, and themable, blame annotation at the end of the current line

  https://github.com/eamodio/vscode-gitlens/tree/v11.2.1#curre...