I usually do commits for small changes but sometimes that means that I have a bunch of local commits and is easy to lose track of where I've made modifications to a file before pushing my changes, specially for big files.
Right now I know I know which lines are not staged (green for new, blue for edited) and maybe when I commit locally, highlight those lines in a different color (purple?) to represent "committed but unpublished."
I also find the behavior odd that if I git add something that the gutter highlights disappear for that file. I would like to keep highlights for anything that hasn't been committed. I suggest a new color for "staged" changes.
FYI the gutter highlight support is built into the vscode git extension and is not provided by GitLens. While would also love to have this feature -- it might best be implemented in vscode's git extension. Definitely worth opening a feature request for them as well.
This would also be useful for branches or commits that are not on master (in case you're on a detached branch, such as FETCH_HEAD). Both use cases are for reviewing PRs while working with the actual code (not diff views), especially when you want to view all changes at once, and not by commit.
All other IDEs do it this way. We really need a new color for stages but uncommitted changes.
Edit: Nevermind. What I want is https://github.com/microsoft/vscode/issues/60389.
A version of this is supported in GitLens 11 -- via the _Gutter Changes_ file annotations
It is limited because of the VS Code apis, but it does provide some of the desired functionality.
Please open new issues/requests for anything missing that you'd like to still see. Thanks!
Most helpful comment
I also find the behavior odd that if I
git addsomething that the gutter highlights disappear for that file. I would like to keep highlights for anything that hasn't been committed. I suggest a new color for "staged" changes.