If you want to use a custom workflow that is not catered to by the Vercel Git Integrations, you may wish to use Vercel CLI to do so. This article covers some of the common use cases and tips on how to use the CLI successfully.
For multiple environments beyond the provided Production, Preview, and Development, or to map a single repository to multiple projects, skipping the project linking step may be required. You can do so by using the following command:
VERCEL_ORG_ID=<value> VERCEL_PROJECT_ID=<value> vercel
Below is an example of a production deployment to a given team with a custom
VERCEL_ORG_ID=<value> VERCEL_PROJECT_ID=<value> vercel --prod --scope <value> -A production.vercel.json
In the examples above, the following attributes are used: