Problems with maintaining our own copy of client repos for tests/deployment #42
Description
Currently for NRGI we're maintaining a fork of the NRGI code in our OpenDataServices organisation - and it's this fork we're using to do tests and deployments from. To keep both of these up to date, me and @caprenter are both set up to push to both repos at once - #38
However, we're still using the NRGI repo for issues and pull requests. This is fine for the most part, put I've been tripped up a couple of times because merging a pull request in the UI only merges it in the NRGI repo. To get travis to see it, I need to remember to pull and then push again locally.
The solution to this might just be to remember to pull and push, or we may want a more automatic way of keeping the two repos in sync. I'm wary of automating this too much though, because one of the advantages of having our fork is it gives us more control over what then gets pushed onto our servers...