End-to-end, UI, or regression tests often test multiple released software components or services together. These services might be built and deployed separately on different schedules. As such, it's important to capture the deployed version of each component when recording test results.
However, the source code for each component is typically not available at the test stage, so recording this information is challenging. To help with this, you can now specify a commit hash for each component's repository when you record a build instead of having the CLI grab the commit hash from repos checked out locally.
This means you don't need to check out your code repositories in the test stage. Instead, you just need to store the deployed version of each service and pass that into the CLI.
To see more about how to do this, check out the documentation: https://docs.launchableinc.com/sending-data-to-launchable/recording-builds-from-multiple-repositories#multiple-repositories-built-deployed-separately-then-tested-together-e.g.-microservices