Default Preview Environment

If TRIGGER_SECRET is configured to point to the Preview environment, but there is no preview deployed for TRIGGER_PREVIEW_BRANCH, default to either another environment or a default preview.

Our use case:

• We only want to deploy Trigger.dev previews for Pull Requests if task-related code is changing, so we don’t exceed our preview env limit.

• We deploy PRs to Vercel preview deployments. We want Vercel previews to default to our TDev Staging env if there is no TDev preview deployed.
  

Our current workaround:

• Vercel preview env’s default TRIGGER_SECRET points to TDev Staging.

• If we are changing Trigger-related code in a PR, we manually run a GH Action to:

  • Deploy a TDev preview.

  • Update the Vercel preview env var TRIGGER_SECRET to point to TDev preview.

  • Redeploy Vercel preview

This is very manual and slow, so not ideal.

Proposal:

• In the TDev Preview branch manager, add the ability to designate a preview as the “default”.

• Bonus: Add the ability to connect to GitHub and optionally deploy previews for PRs only when task-related code has changed.
  

Alternative:

• Make preview branches unlimited :)
  

I read somewhere that it’s being considered to just make Staging a preview environment - maybe this slots in to that work.

Loving the previews btw!