GitLens

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

[Eric Amodio 🦋 @eric.amod.io @eamodio]

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

[GitLens @gitlens]

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:
https://t.co/oZLYmykmTQ

[GitKraken @GitKraken]

@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:
https://t.co/eSG0QO5GMv

[GitLens @gitlens]

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:
https://t.co/tn0TlXxBoM

[GitLens @gitlens]

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

[GitLens @gitlens]

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

[Chris Griffing @cmgriffing]

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

[MediaRon @MediaRonLLC]

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

[Joel Stransky ✨ @JoelStransky]

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

[rolex.dev @rolex_devv]

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

[Khush Shah @khush2808]

This extension is so awesome.
@gitlens

[Nicu Chiciuc ▣ @nicu_tsx]

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

[Ayush ☘️ @ayushHardeniya]

@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👇

[Chris Griffing @cmgriffing]

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