Is the .github/workflows/deploy-sanity.yml really needed?

[JamesSingleton]

I noticed that if you add the items that are listed in .env.sample for the studio in the turbo.json as well as the projects environment variables and deploy via Vercel that everything just works without needing the GitHub workflow.

[markbebbington]

I've been getting my head around this recently too coming from a WordPress background.

My understanding is the GitHub Actions workflow is for deploying your Sanity Studio to Sanity's hosting (my-project.sanity.studio), which is separate from your Next.js frontend that Vercel handles.

It isn't strictly necessary, you can skip it and just run npx sanity deploy manually when you update your studio, but I've found the workflow to be super convenient - automatically keeping my hosted studio in sync when I push schema changes.