Ask HN: How do you organize your micro services (version control)

So I was recently able—through sheer force of will (ie. I just went ahead and did it)—to get my company onto a more modular micro service style architecture for the next generation of our platform.

It's great having each small piece handle a very specific task, and it keeps the code bases small and easy to maintain. However, the rub has been organization and issue tracking. I charged ahead, making a new git repo for each service (as this made sense and they all had separate dependancies (though some shared)), and now, it's difficult for folks to know where to file issues, but it also can be a bit of a chore getting a service running as you need to collect the necessary pieces.

Currently, we are using naming conventions to organize the projects as best we can, but I wonder if anyone has any tips for managing a modular architecture and not letting things get too out of hand?