Working Copy work around for INI files (and probably other non-py files)
I've recently been using Working Copy as a means of distributing code between devices and with the new integration it works wonderfully (as I am slowly learning). However,...
Working Copy does not allow me to move my config.ini into Pythonista and thus breaks my code, or at least it will no longer run.
Question: What am I doing incorrectly, or barring that what is the work around to move non-py/config files from Working Copy into Pythonista?
Thank you in advance,
Does working copy let you edit your .gitignore file? Could be you have .in files ignored...
@JonB - Thanks for the interest.
I found a work flow that does include my INI files.
The curious thing is about this is by "select"-ing the full directory does include the INI file when opening in Pythonista. However, if you merely open the directory (and then view all of the individual files within the directory), the INI file(s) and in my case README is grey and un-selectable (if that is a word). If you then click "select all", you do not get the INI file(s) or README.
I do not quite understand why this would be the case, but there is an actual, reasonable path for me to move forward.
The integration took me a while to figure out, but only because it was so simple that I never considered it. Very nice integration work.