Files created in subfolders still not shown with refresh command

From the glitch terminal I created a sub folder called test-project

The folder is populated with a few files and more subfolders. The glitch faq says running the refresh command will update the file view and show files in the project.

Unfortunately the command does not show any files in the subfolder.

Also from the editor I tried creating a test-project/somefile.js which was made and shows in the file pane but after running refresh in the console disappears from editor (but still on disk).

Glitch Project

Edit: files created outside the sub folder do seem to get added to the files pane

Hmm looks like the sub folder had a .gitignore and deleting the .gitignore and running refresh made the sub folder files show up in the editor.

Contents of the .gitignore
$ more .gitignore
################################################
###############  .gitignore   ##################
################################################
#
# This file is only relevant if you are using git.
#
# Files which match the splat patterns below will
# be ignored by git.  This keeps random crap and
# sensitive credentials from being uploaded to 
# your repository.  It allows you to configure your
# app for your machine without accidentally
# committing settings which will smash the local 
# settings of  other developers on your team. 
#
# Some reasonable defaults are included below,
# but, of course, you should modify/extend/prune
# to fit your needs!
################################################




################################################
# Local Configuration
#
# Explicitly ignore files which contain:
#
# 1. Sensitive information you'd rather not push to
#    your git repository.
#    e.g., your personal API keys or passwords.
#
# 2. Environment-specific configuration
#    Basically, anything that would be annoying
#    to have to change every time you do a 
#    `git pull`
#    e.g., your local development database, or
#    the S3 bucket you're using for file uploads
#    development.
# 
################################################

config/local.js





################################################
# Dependencies
#
# When releasing a production app, you may 
# consider including your node_modules and
# bower_components directory in your git repo,
# but during development, its best to exclude it,
# since different developers may be working on
# different kernels, where dependencies would
# need to be recompiled anyway.
#
# More on that here about node_modules dir:
# http://www.futurealoof.com/posts/nodemodules-in-git.html
# (credit Mikeal Rogers, @mikeal)
#
# About bower_components dir, you can see this:
# http://addyosmani.com/blog/checking-in-front-end-dependencies/
# (credit Addy Osmani, @addyosmani)
# 
################################################

node_modules
bower_components




################################################
# Sails.js / Waterline / Grunt
#
# Files generated by Sails and Grunt, or related
# tasks and adapters.
################################################
.tmp
dump.rdb
################################################
# Node.js / NPM
#
# Common files generated by Node, NPM, and the
# related ecosystem.
################################################
lib-cov
*.seed
*.log
*.out
*.pid
npm-debug.log
################################################
# Miscellaneous
#
# Common files generated by text editors,
# operating systems, file systems, etc.
################################################
*~
*#
.DS_STORE
.netbeans
nbproject
.idea
.node_history

Don’t see anything in particular that would hide all the contents of the sub folder.