Allow decoupling of PR previews from production branch

[valentinbeggi]

Hi Mintlify team,

Quick feature request.

We use a release-based deploy flow: PRs merge into main, and on release we push to a dedicated "mintlify" branch configured as our production branch. This way, merges to main don't trigger doc deploys, only releases do.

The downside is that since PRs target main (not the prod branch), we don't get automatic PR preview deployments.

Would it be possible to either:

• Let us configure PR previews to trigger on PRs targeting any branch (not just production), or
• Provide an API to programmatically create/refresh preview deployments?

Happy to discuss further if helpful. Thanks!

Valentin

[jalaziz]

We use the same release flow, where we cut a dedicated release branch to indicate a release.

The high-level full workflow is:

• Engineers develop against main and create PRs against main.
• Periodically, we cut a release branch (e.g. release/XXXXXX) and promote that through a series of QA environments until it hits production.

To support this workflow, we would like to be able to:

• Configure the base branch (main) for PR previews.
• Configure a separate "live" branch.
• Utilize an API to switch the "live" branch via our deployment pipeline.

[sheppy-atai]

I'm in a similar situation. I need the ability to have the majority of my changes to to a branch that's the "on-deck" branch containing all the changes that need to publish with our next product release, but still also be able to use the same tools to create PRs that I will merge directly to main when I need to update the current release's docs.