vercel pull

The vercel pull command is used to store Environment Variables and Project Settings in a local cache (under .vercel/.env.$target.local.) for offline use of vercel build and vercel dev. If you aren't using those commands, you don't need to run vercel pull.

When environment variables or project settings are updated on Vercel, remember to use vercel pull again to update your local environment variable and project settings values under .vercel/.

vercel pull

Using the vercel pull fetches the latest "development" Environment Variables and Project Settings from the cloud.

vercel pull --environment=preview

Using the vercel pull fetches the latest "preview" Environment Variables and Project Settings from the cloud.

vercel pull --environment=preview --git-branch=feature-branch

Using the vercel pull fetches the "feature-branch" Environment Variables and Project Settings from the cloud.

vercel pull --environment=production

Using the vercel pull fetches the latest "production" Environment Variables and Project Settings from the cloud.

These are options that only apply to the vercel pull command.

The --yes option can be used to skip questions you are asked when setting up a new Vercel Project. The questions will be answered with the default scope and current directory for the Vercel Project name and location.

vercel pull --yes

Using the vercel pull command with the --yes option.

The following global options can be passed when using the vercel pull command:

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --scope
• --token

For more information on global options and their usage, refer to the options section.