Currently, if a repo builds a Docker image that needs to be mapped to multiple services (e.g., web, api, worker), the only current solution is to have each service connect to the same repository.
However, this feels a bit wasteful because, in reality, you only need to build once, and the final image could be reused...
Perhaps one implementation method is to allow a service's source to be configured directly as another service's image. This way, not only for Docker builds, but even for third-party Docker images, updating one could update all related services simultaneously.