Vercel deployment

Help
2

Hi, @muditgarg-renticklec!

I noticed your issue is related to these recent discussions:

All these cases are hitting the same core limitation: Vercel prevents multiple environments from automatically deploying from the same branch. This is designed to prevent deployment conflicts, but it can be challenging when you need different domains/environments (like your DomainA and DomainB) to deploy from the same branch.

I’ve shared similar solutions in the other threads, but here are some potential solutions:

  1. Use separate branches as this gives you the cleanest separation of concerns.

    1. preview branch for DomainA deployments
    2. dev branch for DomainB deployments

  2. Use Vercel’s promotion workflow. This maintains your desired staging → production flow.

    1. Deploy to DomainA first
    2. Use Vercel’s promotion feature to promote to DomainB when ready

  3. Set up a custom CI/CD pipeline:

    1. Keep your current branch structure
    2. Use GitHub Actions to trigger appropriate deploy hooks in sequence
      This gives you the most control over the deployment process.

Let us know how you get on!