Hi Tim

Thanks, we don't currently use IPM.

So essentially if we want to use this we would need to change our current namespace setup and create a development namespace for each developer, plus one basketball stars for the master repository. Then for testing if we wanted multiple testers wanting to test multiple branches at the same time, presumably they'd also need a separate namespaces?

The settings I have in my outgoing namespace are:

and the settings I have in my incoming namespace (where I was trying to pull the project to) are:

I did originally have the settings for the receiving namespace very similar to the outgoing, but when I saw that the exported files had all been put underneath the csp directory I changed them to the above, but they still didn't import. 

The error I am getting is "Unable to import file *** as this is not a supported type"

thanks

From my experience, git-source-control works best with separate dev namespaces per developer. Shared namespaces cause conflicts. For static files (.js, .css, .png), import isn’t natively supported yet—you’ll need custom handling or a workaround script.