Hello guys, I've got some bug with tree view - when I attempt to add a git-ignored subfolder B of project A as separate new project B, it displays as grayed out. If in project A I do remove folder B from .gitignore, then immediately project B becomes colorised.
My workflow based on idea that my Main Application have Apps subfolder in it, which is ignored by .gitignore. Apps subfolder can contain different sub-applications in it, which can be separate git-repos (basically git in git, but not submodules, because Main Application doesn't depends on them). So I want to be able keep this sub-applications in their Apps subfolder of Main Application (because this sub-applications can only be launched within Main Application), but be able to add them as separate New Project folder without influence of .gitignore rules from Main Application project.
Hello guys, I've got some bug with tree view - when I attempt to add a git-ignored subfolder B of project A as separate new project B, it displays as grayed out. If in project A I do remove folder B from .gitignore, then immediately project B becomes colorised.
My workflow based on idea that my Main Application have Apps subfolder in it, which is ignored by .gitignore. Apps subfolder can contain different sub-applications in it, which can be separate git-repos (basically git in git, but not submodules, because Main Application doesn't depends on them). So I want to be able keep this sub-applications in their Apps subfolder of Main Application (because this sub-applications can only be launched within Main Application), but be able to add them as separate New Project folder without influence of .gitignore rules from Main Application project.
For simplicity I'll add simple scheme below: