1- bug fixed

2- turned on notifications so I know of bugs posted in this project, lol

3- not sure why you need to skip the installer. Is it because it is complaining when it comes back about not allowing to be there, and/or complaining when it has gone missing when pulling something touching it?
You can make empty files 'install_ok' and 'install_locked' to stop Composr/Composr complaining. install_ok stops Composr complaining. install_locked stops anyone running the installer.

I think because I didn't stage and commit it, it was stopping newer updates from being carried across. Not sure, but that's how it seemed. I just read up on how to ignore it, will try that now the installer is fixed.

Not sure why you'd change it though? I just keep normal installer in git and re-run when needed. Or were you making some improvements :)?

Just pushed the fix now.

I cloned the repository, and cos I deleted the install.php (as required after install) it was sat there waiting to be staged/committed again. I was looking for an option in the Git for Windows GUI to ignore that file and couldn't find one, and none of your recent changes (at the time) were getting synced. I assumed it was cos that file was sat there, and needed something doing to it first. Not really sure of the best way to keep the local copy updated with the latest commits, some search results say fork it on github (which I have done) and then pull from that. I really have no idea what I'm doing so I'm gonna stick to reinstalling from the zip archive until I have worked it all out.

Right, so that's what I thought it was.

Just make those empty install_ok and install_locked files and you'll be sorted :).

Okay, that sounds easy enough, so I need to make 2 files, called install_ok and install_locked?

yes