Open JonathanAaron opened 8 years ago
There is a reason for the current behaviour, which is that it is (very) convenient for local development to be able to edit files in place without having to push back to the remote repo. So there is a dirty check, and if the repo is dirty we don't attempt to pull, and this is quite useful IMO. I think maybe your "workaround" should just be documented as best practice for repos that contain both code and configuration.
So I have my config server and webservices in the same repo. I'll make a new branch and do some work. When I start up the ConfigServer and start code/testing it automatically switched back to master. Since I have my webservices in the same repo it switches those too.
It appears that it isn't coping the repo.