How to Deploy a Project with Private Git Submodules to Vercel
When building with Vercel, you cannot retrieve submodules that are set as private repositories.
Even if you grant permissions to the Vercel app on Github, it won't work.
You need to retrieve them using an HTTP fine-grained personal access token.
1. Create a fine-grained personal access token
Go to the following page: https://github.com/settings/tokens?type=beta
Click on "Generate new token."

For Repository access, select "Only select repositories" and choose the minimum necessary repositories.
For Repository permissions, grant Read-only access to Contents only.

Click the "Generate token" button to create the token.
2. Register the token as an environment variable in Vercel
Register it in the Settings → Environment Variables section of your Vercel project. I registered it under the name GITHUB_PAT.

3. Create a build script
Create a file named sh/build-for-vercel.sh.
Recommended: Using GIT_ASKPASS
Embedding tokens directly in URLs poses a security risk, so using GIT_ASKPASS is the recommended approach.
GIT_ASKPASS is an environment variable that specifies a script to be automatically executed when git needs authentication credentials. It is safe because the token is not stored in the URL or git config.
#!/usr/bin/env bash
cd $(dirname $0)/../ || exit
set -e
if [ -z "${GITHUB_PAT}" ]; then
echo "The environment variable GITHUB_PAT is not set. Please regenerate the GitHub Fine-grained token and register it as the GITHUB_PAT environment variable in Vercel."
echo "https://github.com/settings/tokens?type=beta"
exit 1
fi
# Pass token via GIT_ASKPASS (no token in URLs)
ASKPASS_SCRIPT="$(mktemp)"
trap 'rm -f "${ASKPASS_SCRIPT}"' EXIT
cat > "${ASKPASS_SCRIPT}" <<'SCRIPT'
#!/usr/bin/env bash
case "$1" in
*Username*) echo "x-access-token" ;;
*Password*) echo "${GITHUB_PAT}" ;;
*) echo ;;
esac
SCRIPT
chmod 700 "${ASKPASS_SCRIPT}"
export GIT_ASKPASS="${ASKPASS_SCRIPT}"
export GIT_TERMINAL_PROMPT=0
git submodule set-url <my-submodule> "https://github.com/ytyng/<my-submodule>.git"
git submodule sync
git submodule update --init
# Your original build script
npm run generate
Key points:
- The temporary script specified by
GIT_ASKPASSautomatically provides the token when git requests authentication trapautomatically deletes the temporary script after the build completes- The token is not included in the submodule URL, so it never persists in git config
GIT_TERMINAL_PROMPT=0disables interactive prompts
Previous method (not recommended)
The following method embeds the token directly in the URL. It works but has security risks, so the GIT_ASKPASS method above is recommended.
#!/usr/bin/env bash
cd $(dirname $0)/../ || exit
if [ -z "${GITHUB_PAT}" ]; then
echo "The environment variable GITHUB_PAT is not set. Please regenerate the Vercel submodule token on Github and register it as the GITHUB_PAT environment variable in Vercel."
echo "https://github.com/settings/tokens?type=beta"
echo "https://vercel.com/<my-own-projects>/<project-name>/settings/environment-variables"
exit 1
fi
git submodule set-url <my-submodule> "https://${GITHUB_PAT}@github.com/ytyng/<my-submodule>.git"
git submodule sync
git submodule update --init
# The original build script
npm run generate
4. Write the vercel.json
Since this is for generating static content with Nuxt, it will look like this:
{
"buildCommand": "sh/build-for-vercel.sh",
"outputDirectory": ".output/public"
}
Note
At the beginning of the build, you will inevitably see the warning:
Warning: Failed to fetch one or more git submodules
but you can ignore it.

Additional Information
You can also make it work by re-cloning instead of updating the submodule.
rm -r <my-submodule>
git clone --depth 1 --branch main "https://${GITHUB_PAT}@github.com/ytyng/<my-submodule>.git" <my-submodule>
We look forward to discussing your development needs.