Edward Diener wrote:
I know for my individual testing if my library X/develop needs something from library Y/develop I pull from library Y/develop in order to test.
What you do for your individual testing is separate from what the test infrastructure does. You have a local repository, in which you can have a local X/develop branch that you test against the remote Y/develop. This is independent of what others see. Of course, if the testing infrastructure tests your remote X/develop against Y/master, you can't push your changes to Github until Y/develop is merged to Y/master on Github. Then again, one might well argue that your development in this case ought to happen on a feature branch that is not develop. (And the same can also be said about Y's development.) Anyway, as I said, both testing systems have their pros and cons. We'll need to pick one and settle on it before real development can resume, though.