@native-api: Thanks for the link. It appears that I’ll need to get comfortable with submodules.
But you can help me with one question before I go charging down the wrong path: To facilitate usage, mulib library is minimal by design and does not contain the unit tests. Rather, I chose to do it the other way around: mulib-support contains the unit tests, and conceptually owns mulib as a submodule (although at present it’s just a subdirectory, not a submodule).
Given that: can I assume that all the instructions you gave in How to trigger a build in the test project upon a commit to dev project with Travis CI API - #2 by native-api still apply as long as I flip the meanings of test repo and dev repo?