I’m getting an error while trying to build a simple hugo static page.
After successfully initializing the build environment, I get “Failed: error occurred while updating repo submodules”.
I checked the resolution in Pages build error: Failed: error occurred while updating repo submodules, and verified that the .gitmodules includes both the
url field as well as points to a public git repo.
Most likely cause is a private submodule. Is the repo for that submodule a private repository?
If not, could you please share the repo if it’s open source so we can take a look? Alternatively, if you can send the deployment ID (the UUID in the URL) I can check it
The repo in the submodule seems to be public:
path = themes/hello-friend-ng
url = https://github.com/rhazdon/hugo-theme-hello-friend-ng.git
Here’s the deployment UUID:
Looking at our logs I see:
Cloning into '/opt/buildhome/clone/themes/hello-friend-ng'...
fatal: remote error: upload-pack: not our ref 581742d567f1b78fbeee9b519b7e767888749fce
fatal: the remote end hung up unexpectedly
Fetched in submodule path 'themes/hello-friend-ng', but it did not contain 581742d567f1b78fbeee9b519b7e767888749fce. Direct fetching of that commit failed.
The commit of that submodule is no longer accessible. It was possible there was a force push and the commit is no longer there. If you just pull the latest changes into the submodule that should fix it
Great! I updated the submodule and now points to a publicly accessible commit.
This is probably in your roadmap, but is there a way to get access to more verbose error messages?
Yes better error messaging is definitely on our roadmap!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.