Eric Amodiois creating GitLens for VS Code
Select a membership level
You are an individual that benefits from GitLens, my other open-source extensions or projects, or the VS Code Development Community Slack and you want to help support my work. Going the extra mile — Thanks!
- Your name will be added to the BACKERS.md in the GitLens repo
About Eric Amodio
Hi.I'm Eric Amodio, an open-source enthusiast and maintainer. I ❤ open-source — both building and contributing. I love the collaboration and the sharing of knowledge driven by the open-source movement. At the same time, open-source comes with a time cost, of which gets paid by trading time from other areas (for me usually sleep 💤). Of course, by becoming a patron of me and my work, you can't create time, but you can certainly help increase the reward aspect of trading this precious time and help ensure that it continues.
I spend a lot of my time building GitLens for VS Code and have for well over 3 years now. From its very humble beginnings, GitLens has grown wildly beyond my expectations — in both its reach as well as its demands on my time and attention. GitLens now has over 3.5 million installs and is used by teams of all sizes, from single devs to enterprise teams. I also author and maintain many other VS Code extensions (and ideas for many more) as well as contribute to many open-source projects.
💖 Thank you for your future patronage!
About GitLensGitLens is an open-source extension I created for Visual Studio Code. While GitLens is generously offered to everyone free of charge, if you find it useful, please consider supporting it.
GitLens supercharges the Git capabilities built into Visual Studio Code. It helps you to visualize code authorship at a glance via Git blame annotations and code lens, seamlessly navigate and explore Git repositories, gain valuable insights via powerful comparison commands, and so much more.
GitLens simply helps you better understand code. Quickly glimpse into whom, why, and when a line or code block was changed. Jump back through history to gain further insights as to how and why the code evolved. Explore the history and evolution of a codebase.
FeaturesHere are just some of the features that GitLens provides,
- an unobtrusive current line blame annotation at the end of the line with detailed blame information accessible via hovers
- on-demand gutter blame annotations, including a heatmap, for the whole file
- authorship code lens showing the most recent commit and # of authors to the top of files and/or on code blocks
- on-demand gutter heatmap annotations to show how recently lines were changed, relative to all the other changes in the file and to now (hot vs. cold)
- on-demand recent changes annotations to highlight lines changed by the most recent commit
- a status bar blame annotation showing author and date for the current line
- many rich Side Bar views
- a Repositories view to visualize, navigate, and explore Git repositories
- a File History view to visualize, navigate, and explore the revision history of the current file
- a Line History view to visualize, navigate, and explore the revision history of the selected lines of current file
- a Search Commits view to search and explore commit histories by message, author, files, id, etc
- a Compare view to visualize comparisons between branches, tags, commits, and more
- many powerful commands for exploring commits and histories, comparing and navigating revisions, stash access, repository status, etc
- supports user-defined modes for quickly toggling between sets of settings
- and so much more
Recent posts by Eric Amodio
How it works
Get started in 2 minutes
Choose a membership
Add a payment method