Pulling CLI Environment Variables

[awlevin]

Hi all. What's the recommended approach to connecting to a Vercel project and pulling environment variables? We're about to onboard new teammates and I like the idea of them being able to run vercel env pull to configure their local environment in 1 step. But I can't find a way to locally link our git repo to our Vercel project without full on redeploying it.

It seems like just committing .vercel/project.json would solve this (provided a person logs into the CLI and runs vercel switch to select our team instead of their personal account... but the .vercel/README.txt warns against committing these files. Nothing in .vercel/project.json looks particularly sensitive, but I imagine if they're recommending against committing it, there could eventually be sensitive information in there.

For now I guess we'll just continue manually sharing our environment configs with one another. Requiring a full-on deploy to link a local repo to a project seems unnecessary.