GitLens @gitlens

GitLens is the #1 Git extension for @code & part of @GitKraken’s DevEx platform: orchestrating agentic workflows with 40M+ devs at 100K orgs 🚀 gitkraken.com/gitlens Joined December 2018

Tweets

362
Followers

1K
Following

4
Likes

189

Eric Amodio 🦋 @eric.amod.io @eamodio

a week ago

Great improvements to the massive 18 release and a TON of performance improvements too!

GitLens @gitlens

a week ago

GitLens 18.1 is now available, with performance improvements, Commit Graph refinements, and quality-of-life updates to make your daily Git workflows smoother. Grab the update and see what’s new: help.gitkraken.com/gitlens/gitlen…

0 1 2 359 0

0 1 4 272 0

View Details

GitLens @gitlens

a week ago

0 1 2 359 0

View Details

GitKraken @GitKraken

3 weeks ago

@gitlens 18 is LIVE! If your repo is starting to feel chaotic from coding agents, parallel work, and worktrees everywhere… GitLens 18 is probably the cleanest workflow upgrade you can make right now. Better Git workflows for the agent era. Read the full GitLens 18 release notes here: help.gitkraken.com/gitlens/gitlen…

0 1 3 169 0

View Details

GitLens @gitlens

3 weeks ago

If your repo is starting to feel chaotic from coding agents, parallel work, and worktrees everywhere… GitLens 18 is probably the cleanest workflow upgrade you can make right now. Read the full GitLens 18 release notes here: help.gitkraken.com/gitlens/gitlen…

0 0 1 28 0

View Details

GitLens @gitlens

3 weeks ago

🧪 Agent Kanban is kind of wild. Your active coding agents automatically organize into Kanban boards for: • Needs Input • Working • Idle • Inactive This is an experimental feature so try it out and let us know what you think.

1 0 1 27 0

View Details

GitLens @gitlens

3 weeks ago

Your repo after a few weeks of coding agents: 🌿 branches everywhere 🤖 agents everywhere 📂 worktrees everywhere 😵 context nowhere GitLens 18 is our answer to that. The Commit Graph became a workbench for parallel development. 🧵

1 2 2 421 0

View Details

Chris Griffing @cmgriffing

2 months ago

I would just like to remind people that there are simpler ways to get the Pull Requests via the API. Things like *cough* @GitKraken and @gitlens

mark @r_marked

2 months ago

absolutely insane workaround suggestion

19 19 908 43K 24

1 2 7 889 1

View Details

MediaRon @MediaRonLLC

2 months ago

@cmgriffing @GitKraken @gitlens Love GitKraken. Huge learning curve at first admittedly, but now it’s all second nature and I wouldn’t trade it for any other client.

0 2 4 305 0

View Details

Joel Stransky ✨ @JoelStransky

2 months ago

Thank you @GitKraken for making it easier to see where any branch came from within @gitlens

0 2 5 447 0

View Details

rolex.dev @rolex_devv

4 months ago

I can't believe that I've had @gitlens for ages but never used most features aside blame annotations on hover, commit graph and occasional diff views for files. I just went through the docs and found out I can - Create PRs - Generate detailed commits with AI - + lots more

0 1 3 138 0

View Details

Khush Shah 📈 is building cool things @khush2808

4 months ago

This extension is so awesome. @gitlens

0 1 1 101 0

View Details

Nicu Chiciuc @nicu_tsx

2 months ago

I think the main reason @gitlens looks so good is because they include the avatar of the user inside the circle of the commit. That way I don't have to drag my eyes all the way to the right to see the name of who made the commit. I even set my gravatar to be a more vibrant color so I can easily see my commits

0 1 3 725 0

View Details

@

2 months ago

@gitlens is lowkey clutch...fr ever been stuck mid-rebase or untangling 100+ commits after a messy upstream pull? yeah, same. it actually lets you see what git is doing - commits, branches, blame, all of it if git trees confuse you, just try it drop ur thoughts below👇

0 1 3 89 0

View Details

Chris Griffing @cmgriffing

6 months ago

With a good @Code extension (*cough* @gitlens) or desktop GUI (*cough* @GitKraken), worktrees are even easier to get started with.

Andrea @acolombiadev

6 months ago

Stop stashing. Use git worktrees. git worktree add ../my-project-main main cd ../my-project-main git worktree remove ../my-project-main Three commands. Same Git history, separate folders. Works great for AI tools running parallel tasks too. More tips like this in Main Branch