There was an original issue where (I think) some change had been made it the Git repo where the cached version of the repo in the build cache was in a state where updating the repo was failing:
5:56:06 PM: Starting to prepare the repo for build
5:56:06 PM: Preparing Git Reference refs/heads/master
5:56:10 PM: Error fetching branch: https://x-access-token:v1.<redacted>@github.com/thunderrabbit/barefoot_rob refs/heads/master
5:56:10 PM: Failing build: Failed to prepare repo
5:56:10 PM: failed during stage 'preparing repo': exit status 1
5:56:10 PM: Finished processing build request in 13.965550458s
The usual solution for that is to build while clearing the build cache to get a fresh clone of the repo. Here is a screenshot of that setting in the UI:
I actually tried this for that site already. This new deploy attempt is now showing errors for the submodule SSH keys not working:
This is almost certainly because the repo was re-linked. Re-linking does reset the SSH key used. This is the new public key to add at GitHub for this site:
You can use this key with multiple private submodules attached to the same repository, but that does take some extra work since GitHub does not allow Deploy Keys to be used in multiple places. You’ll have to instead add them to a user (perhaps you? or maybe a robot-account that you create on GitHub) that has access to all repos.
If there are other questions about this, we’ll be happy to answer.