Git status in File Explorer

[ozsay]

Similar to what atom provides in the project explorer:

1. New files are displayed green.
2. Modified are displayed yellow/orange.
3. Ignored files are displayed transparent-ish.

Thanks

[HQidea]

and

• files which were merged with conflicts are displayed red,

it's very convenience to distinguish conflicted from others

[joeshub]

+1 Having to toggle back and forth between the Git <> Explorer views is super unproductive.

Ideally it would be possible to also see the changeset as a group on top where we have Open files, as well as a nested tree of changes visualized by color (as shown by @abdonrd above.)

[joaomoreno]

Come one guys, just stop with the +1.

Please place a thumbs up on the first post.

[tkafka]

I've got an interesting use case and argument to make a generic API that would allow plugin to color individual files and folders:

File/folder aging similar to Trello aging powerup - I'd like the files and folders that haven't been touched for a long time (judged by git history) to fade out, so that the 'working set' would be more distinct and easier to find.

Why: I have a large repo of tiny projects (think a bunch of scripts for analytical report) where 90+ % of work won't be touched again (but I can't move old stuff to subfolder because it would break a lot of links pointing to repo).

If there was an API endpoint for coloring tree items, I could write a plugin that reads the git log and colors each file/folder according to some set of rules.

[wclr]

So what about it, isn't there still API that allow to create extension for this, or will this be implemented as integrated feature?

[mjmarianetti]

Any update on this?

[ghost]

+1

[foobarable]

+1

[thevikas]

+1

[wilomgfx]

Can you guys please stop +1 ing and spamming our mail inboxes ???

It serves no purpose at all.

[adamgajzlerowicz]

+1 to no spamming xD

[matti]

protip: filter out messages from github where the body equals/matches/lolwuts "+1"

you can't stop these people.

[LaurentTreguier]

@jmbelloteau as @fredrikaverpil said earlier in the comments, VSCode issues are sorted by the number of thumbs up to the original comment. So commenting "+1" instead of adding a reaction to the first comment is indeed spamming, as it's not the correct way to provide feedback and only sends useless emails to everyone. And contrary to adding a reaction, it won't even be taken into account.

[BenGale]

+1

[ferrannp]

I am so used to this in Webstorm too :D. But as I can see this will probably be developed sooner than later. Here is a screenshot from Webstorm for inspiration (following @abdonrd):

Ah, also untracked files are shown as red!

[daviddarke]

+1

[semi-sentient]

Just gave VS code a try for the first time today (coming from Atom) and one of the first extensions I searched for was "git status" highlighting in the explorer view. The "source control" tab on its own is very nice, but having folders/files highlighted allows me to quickly navigate to the component that I'm working without having to always leave my directory tree expanded (highly useful for FE codebases that tend to have more deeply nested structures).

[davidhu2000]

ideally, it would be great if the colors are able to be modified individually.

{
    git.newFileColor: 'green',
    git.changedFileColor: 'yellow',
    git.untrackedFileColor: 'blue',
    git.ignoredFileColor: 'gray,
    git.mergeConflictFileColor: 'red'
}

[vothanhdat]

+1

[mmazzarolo]

I've been searching for a while for a good app to remind me to drink water.
Then, I realized that I'm subscribed to this thread.
Keep the +1 coming guys, they're not useless anymore 🚰

[pohmelie]

@mmazzarolo Why you need reminder to drink water? Is it not enough to drink when you thirsty?

[arkon]

Anyway, please stop +1-ing. I'm sure the devs are already aware of this and will post updates as they come.

[mmazzarolo]

@pohmelie that's a valid alternative, thank you!

[kicktheken]

+1

[wilomgfx]

wtf is wrong with these +1 people ?

[westy92]

Great idea, @davidhu2000! It would be nice to support hex colors like git.ignoredFileColor: '#333333', too.

There's a nice list of the types and colors that JetBrains uses here: https://www.jetbrains.com/help/idea/2017.1/file-status-highlights.html (you can inspect the color name to get the hex).

[Letrico]

+1 raising awareness on how much this feature is wanted

[newable]

The only reason that I'm not using VS Code. Too bad :(

[admosity]

Anyone know where in the codebase one might start to implement this? I want to take a stab at it.

[AndreasGassmann]

@admosity Someone already submitted a pull request last year which got rejected: https://github.com/Microsoft/vscode/pull/8462 .

2824 was mentioned as a blocker somewhere above, which has been merged a while ago. I would look at the changes there to make sure it is implemented how the VS-Team wants it.

[admosity]

@AndreasGassmann awesome! I'll take a look through.

[Altiano]

The one last key feature prevents me from switching to vs code

[davidbayo10]

When this feature is incorpored, I'll change to vscode

[pmoleri]

I'm subscribed to this issue because I'd like to know when some progress is done. Everyone is aware of how wanted this feature is and right now is the second most upvoted issue :).

If you really, really want this feature just upvote the first comment, and avoid adding repeated comments.

For people that feel that this feature is neccessary to switch to VS Code. I can say it was the first feature I missed when switching from Atom, but IMO this is a small price to pay for this awesome IDE. What's more, last week I had to do some work in Atom and I really missed VS Code's git view.

[tannerlinsley]

@waderyan This is a dealbreaker moving from atom.

[gaui]

Yes please!

[MartinSchmid2409]

+1

[RichardGarcia]

+1

[anuvratrastogi]

+1

[karabaja4]

I made a very ugly hack that implements this feature by modifying workbench.main.js and injecting the CSS based on git status output. If you don't mind digging through VS Code internal files and having your VS Code execute git status every 5 seconds, take a look.

https://github.com/karabaja4/vscode-explorer-git-status

Update 28.6.2017: Fixed a bug where plugin would not load when reopening the project. Update 30.6.2017: Added highlighting of parent directories of modified files (as Atom does). Update 1.7.2017: File matching is now done using full file or directory path. Before this change the directory was highlighted if it had the same name as another changed directory.

[sanjibukai]

Hello, I cannot figure out if this feature is implemented or not yet? I didn't find any settings nor extensions and as this was opened nearly two years ago, I'm confused..

[arkon]

@sanjibukai The issue is still open, so it hasn't been implemented yet. You can use the hack that @karabaja4 created in the comment above yours though.

[sanjibukai]

I'm new here, but really does it need nearly two years to add this obvious feature? I surprisingly never heard about vscode until recently, but when I heard about it the main feature that was advocated is precisely how vscode is good integrating git. And indeed it's good. What a pity that this feature still lacks.. Nevertheless, keep the good work vscode team 👍

[strctr]

Can't keep focused without this feature. Every time i have to remember which file I edit.

[fro3clr]

+1

[saada]

@karabaja4 why don't you make a PR with your hack and get feedback on how to implement it properly?

[karabaja4]

@saada I would do that if I thought any of that code could be integrated to VS Code. Running a background git status process is surely not a sane way to implement this feature. Any proper code that implements this has to be written from scratch and implemented correctly inside VS Code source framework. That is a lot of work and unfortunately at the moment I don't have sufficient time available. Sorry :(

[cucumbur]

Piling on isn't going to help things when their stated metric is already said to be the numbers of +1's the original post gets, not in replies. Also, considering this is a tool for developers, I'm kind of astonished at how much entitlement and not understanding the open source process there is going on here. The feature request is here as an open issue. You can +1 it on the post and either do it yourself (presumably working with the maintainers to make sure its not in vain) and request a merge or just leave it at that. If its a vital feature for you, then use Atom. As I write this, there are over 4000 open issues. You will have to exercise patience.

(or use @karabaja4 hack in the meantime - thanks for your work!)

[nelreina]

+1 Doing this because just listen to talk devchat and issues with more comments will get more attention

[Kaijun]

@karabaja4 great work. Another approach: how about running git status at init, and then update whenever the onFileSave event is fired? would this be more efficient?

perhaps we could configure the way how we refresh the git status.