Is your feature request related to a problem? Please describe.
My venture into learning and running MicroPython has, so far, been moderately successful. I come from a background in C/C++ on ESP32 using VSC with PatformIO as my preferred IDE.
So I was pleased to find your VSC extension which I have managed to load and use. THANK YOU!!
I am also trying to follow 'good practice' and creating a GIT repository for my project. Along with that I have been creating a README.md file documenting my journey, issues, learnings and some images.
However, I find that all folders and files in my project folder are getting uploaded to my ESP32 using it's precious memory
Describe the solution you'd like
I'd like to have a file structure in the project which would allow me to have files not required to be uploaded to the device but can be committed to GIT
Describe alternatives you've considered
I could create a non-code project in the same code-workspace and save separately to GIT but I think that would confuse and rapidly become obsolete?
Additional context
Perhaps I have missed something? Perhaps the capability already exists? I have reviewed your documentation and the current issues but cannot see a similar request.
Is your feature request related to a problem? Please describe. My venture into learning and running MicroPython has, so far, been moderately successful. I come from a background in C/C++ on ESP32 using VSC with PatformIO as my preferred IDE. So I was pleased to find your VSC extension which I have managed to load and use. THANK YOU!! I am also trying to follow 'good practice' and creating a GIT repository for my project. Along with that I have been creating a README.md file documenting my journey, issues, learnings and some images. However, I find that all folders and files in my project folder are getting uploaded to my ESP32 using it's precious memory
Describe the solution you'd like I'd like to have a file structure in the project which would allow me to have files not required to be uploaded to the device but can be committed to GIT
Describe alternatives you've considered I could create a non-code project in the same code-workspace and save separately to GIT but I think that would confuse and rapidly become obsolete?
Additional context Perhaps I have missed something? Perhaps the capability already exists? I have reviewed your documentation and the current issues but cannot see a similar request.