Repository navigation
Git status in File Explorer #178
Description
Activity
- changed the title
[-]Feature request: Files status highlight according to their source control status[/-][+]Git status in File Explorer[/+]on Nov 19, 2015 - 1
Reacted by Robert Hall, Dimitar Tasev, Nuno Dias, Nelreina, Cristian Orellana Bak, Chris Klapp, Manny Colon and Prem NirmalReacted by Kalle Persson, Mahmoud Saada, Carl Patenaude-Poulin, Grube, Michał Frączkiewicz, Felipe Sabino, Santhosh, Mario Lamontagne, Dan Homola, Ron Waldon-Howe and 66 moreReacted by Borek Bernard, Keegan Farley and Saran Tanpituckpong ✔️Would be cool if this was exposed as an extension in some way. I worry that in some cases, the tree can be a bit polluted with color and look like a Christmas tree. Or if not, at least have the option to toggle it on and off.
Reacted by Glen, Norman Eckstein, Marko Kajzer, Pietro Paolo Ferrari, Alaa Masoud, Grube, Guillaume Giamarchi, Friedemann Sommer, Oskar Karlsson, Benjamin Fry and 48 moreReacted by Lufty WirandaYes I agree. I created a separate issue to have this exposed in extension API (see #1394).
+1
Reacted by Kalle Persson, Mahmoud Saada, Grube, Norman Ramírez, Michał Frączkiewicz, Santhosh, Mario Lamontagne, Ron Waldon-Howe, Fernando Marquardt, arkon and 63 moreWould love that too. The Git tab is very handy but this is for another purpose - having colors like in Atom would be very complimentary to see at a glance what's changed and where (with the color propagating automatically up to the top directory). That's probably the feature I miss the most from Atom.
Usually, you don't have 10s or 100s of modified files uncommitted, so it's unlikely to look like a Christmas tree :)
Reacted by nimrossum, ownagedj, adam, Pratik Chaudhary, Ann Cascarano, C J Silverio, Luke Sweeney, Nelreina, Cristian Orellana Bak, Chris Klapp and 5 moreReacted by Jhony Lucas, Pratik Chaudhary and Niccolo BrogiSo it looks like the PR for this was closed. Benjamin Pasero (@bpasero) João Moreno (@joaomoreno) - any updates on the status of this work?
233 remaining items
Fernando Fleury (@fernandofleury) Nobody said anything about not providing theme managers an API to manage it. My post said nothing of the sort. So your snarky comment, is simply invalid and unwarranted.
Johannes Rieken (@jrieken) said:
Well, it was done on purpose because the selection-foreground color often conflicts with the decoration colors.
I said:
If your issue is themes, it isn't your problem. That is the responsibility of the theme developers to update and accommodate.
The issue would be a conflict between the foreground (actually, it's a background color) color of the file/folder tree item (normal, selected, focused), and the font color choices for the various git statuses.
This would be the responsibility of theme developers. They should choose both the foreground colors of the items in the tree and the font colors for the various git statuses so that they don't conflict.
For example: A theme developer has ThemeX and his font color for the items in the explorer file tree is
yellow. Well, his default font color would conflict with the defaultyellowgit status color. You wouldn't be able to tell which files are modified anymore. So this would be the responsibility of the theme developers! -- The same is for the background color for selected/selected-focused items in the explorer file tree vs the font colors of the git statuses.Is this postponed now?
Reacted by Charles HarrisReacted by Ugo Buonadonna and Charles Harrisiljadaderko I don't think so since it shows up in the upcoming Release Note v1.18 of the next Stable version. The question might be more, will this be closed or is there still more work to be done?
iljadaderko VSCode v1.18 is already out and it includes the changes discussed here.
Are ignored file colors supposed to be a part of the v1.18 update? The docs say
gitDecoration.ignoredResourceForegroundcan be used to color ignored files, but so far I haven't been able to see that affect anything. Modified/untracked coloring works great though. This is on stable 1.18.0, windows.Same here (about ignored color). Hasn't been working for me either, since this whole Git implementation started. Using Insiders.
All thatgitDecoration.ignoredResourceForegrounddoes is ignore ignored files from coloring :)It's working for me and it looks SPECTACULAR.
Reacted by Vlad, Jamie Neubert Pedersen, Felipe Martin and Francesco PasquaReacted by Dillon de Voor and Niccolo BrogiReacted by Johannes RiekenFinally it's here 🥇
Reacted by Jamie Neubert Pedersen, Felipe Martin, Kristijan Sedlak and Francesco PasquaReacted by Vladimir SizikovRobert Hall (@arxpoetica) This is what I get:
How can it work for some and not for others, I don't get it. It's just that one setting
gitDecoration.ignoredResourceForeground
Am I the only one it doesn't work for? Really no one else? :) Oh, and Airuz (@Shurelia)
Has anybody else (us, users) actually tested setting the ignored color before saying it works?OS: Windows 10 PRO (1709)
VSCode: 1.19.0-insider (just updated earlier)
Same on my work laptop and home desktop.Is it in Insiders? How can I use it?
Congrats, everyone!
Niccolo Brogi (@nkkollaw) In both 😎 insiders and stable (1.18)
Mr.Croft (@MrCroft) Please discuss git-ignore issues here: #37857
Reacted by Marian StoicaAs we have shipped this feature in our latest stable build it's time to close and lock this issue. Please create new issues for topic discussions and bug reports. Issues around this area are tagged with the
file-decorations-label.Everyone, thanks for the great and continued feedback that made this feature what it is!
To summarise and repeat my previous comment.
A couple of things
- By default there is a combination of color and bagde.
- enable/disable icons with:
"explorer.decorations.badges": true|false - enable/disable colors with
"explorer.decorations.colors": true|false
- enable/disable icons with:
- Colors show in the file tree, the open editors section, and in the SCM viewlet
- There are three colors to begin with. You can customise them in the
workbench.colorCustomizations-setting. The colors aregitDecoration.modifiedResourceForeground,
gitDecoration.deletedResourceForeground,
gitDecoration.untrackedResourceForeground,
gitDecoration.ignoredResourceForeground, and
gitDecoration.conflictingResourceForeground
- By default there is a combination of color and bagde.
- locked and limited conversation to collaborators
on Nov 9, 2017
Similar to what atom provides in the project explorer:
Thanks