Hi Jason,

I’d edit the post and remove the Team ID and deployment IDs. They are not API keys, but they are still account/project identifiers that usually do not need to be public.

For the clone issue itself, your git rev-parse --show-object-format => sha256 detail is probably the key. GitLab’s SHA-256 repository format is still marked as experimental/not ready for production use, and GitLab also says you can only choose it when creating the project, not migrate that repo back to SHA-1 later:

https://docs.gitlab.com/user/project/#create-a-project-that-uses-sha-256-hashing

For a practical workaround, I’d create a fresh GitLab repo using the default SHA-1 object format and copy the working tree into it:

1
git clone <old-sha256-repo-url> website-sha256
2
mkdir website-sha1
3
rsync -a --exclude .git website-sha256/ website-sha1/
4

5
cd website-sha1
6
git init
7
git checkout -b main
8
git add .
9
git commit -m "Import current website source"
10
git remote add origin <new-sha1-repo-url>
11
git push -u origin main
12

Then connect that new SHA-1 repo to Vercel.

That loses the original Git history unless you do a more careful export/import, but it is the quickest way to test whether the Vercel failure is specifically the SHA-256 object format. If the SHA-1 copy deploys successfully with the same project settings, that would be strong evidence that the Git integration clone path is the blocker rather than your app build.

Hello Ryu thank you for prompt reply. I migrated the existing code to a SHA1 repo as you described and the Vercel integration works as expected.

However, I raised this ticket to mention that problems might arise in the future and Vercel might want to support this as well when it is released officially in the public as it did with the git LFS option that can be found in the settings. So all in all this was more like a feature request than seeking help. The workaround I used so far was to create gitlab-ci piplines that use the vercel cli to deploy to the prod, but I prefer the built-in integration you proposed.

Anyways it might be early for SHA256 integration but this is some food for thought for the Vercel developers.

Thank you again for your help!