Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Question: Experience with Code Editors + Ignored Files?

See original GitHub issue

Hello, I just stumbled across Meta for the first and am trying it out as I’m in that typical mono-vs-multi repo situation. I like the idea of meta, however upon trying it out I ran into an issue pretty quickly. I use Atom, and like other code editors it supports the .gitignore file… so any directories or files that are ignored get grayed-out. This is a big issue for me in that I now lost my indicators that colorize new (green) and modified (orange) files and the like.

I’m curious if others have worked around this somehow with Atom or similar code editors? How do you use meta, but still maintain full git support being that the project folders are listed in the top level .gitignore file?

Thanks for the insight, I appreciate any feedback.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

derkscommented, May 31, 2019

@patrickleet I actually tried that. I had a workspace for the meta repo, and a separate that just included the sub-directory projects… VSCode must be sourcing .gitignore all the way up the parent directory stack because even in that case it was still treating the subdirectories as ignored. I’m at a loss here.

VSCODE: 1.34.0 macOS: Mojave 10.14.4

0reactions

stale[bot]commented, Jul 30, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.