One way to go about this with docker could be having an extra repo for the integration: - app-backend - app-frontend - app-bundle (or simply "app") Your bac

One way to go about this with docker could be having an extra repo for the integration: - app-backend - app-frontend - app-bundle (or simply "app") Your backend and frontend can be independently developed and use semantic versioning, they could run their independent checks like linting and unit tests. The bundle repo could consist of a docker compose file that uses image versions of backend and frontend that are compatible with one another. You can choose to anchor the version to the minor, or revision etc. This way you can bump your versions when they are ready. Also, pushes to your backend or frontend could trigger a build of the bundle repo. I would run there the integration tests. That being said, if the app is relatively simple, I would probably pack everything up in one repo to avoid the overhead.