mob.sh handles a temporary branch in a particular repo. That suffices when all the code being worked on is in that repo. What about when it’s not? Say, for a simple case, when we’re making changes to a REST endpoint and a consumer of it. How do?

For everyone to pass around every potentially involved repo on every handoff without effort, my best idea so far is to use myrepos with this .mrconfig:

[DEFAULT]
git_mob1 = echo MOB_WIP_BRANCH_QUALIFIER="mob1" "$@"
git_mob2 = echo MOB_WIP_BRANCH_QUALIFIER="mob2" "$@"

Then you can say mr mob1 start 25 or mr mob1 next and it'll run on all repos in rapid succession. All done? mr mob1 done followed by mr status to see which repos actually need us to compose a commit message.

So those are my best ideas so far to adapt http://mob.sh to this situation. What else could we try?