Skip to main content
When the Mintlify agent or an automation opens a pull request, it targets the deploy branch configured for your project (usually main). This is the branch Mintlify builds your live site from, so PRs land there by default and publish on merge. If you want changes to go somewhere else, the control depends on how the run was started.

​
Agent runs in Slack, the editor, or the dashboard

For a single agent run, name the branch you want in the prompt. The agent creates the pull request against the branch you name, or pushes commits directly to it when the branch already exists. For example:
  • “Open the PR against the staging branch.”
  • “Push these commits to docs-refresh.”
See Send messages to the agent for the Slack flow and Choose how the agent publishes changes for the workspace-level review process setting that decides between opening a PR and pushing directly to your deploy branch.

​
Automations

Automations always open their pull requests against the deploy branch. There is no per-automation setting to target a different base branch. If you need automation output to land on a non-production branch, point the deployment itself at that branch in Git Settings, or use a separate deployment for that branch and run the automation there. To stop automation PRs from merging without review, set the automation’s update mode to Modify and wait for review on its configure page. See Update mode.