From 583b3f1c21b5340513766f129fb9cb88a4555b24 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 18 Sep 2026 16:18:57 +0000 Subject: [PATCH 1/2] docs: add help center article on agent PR base branch behavior --- docs.json | 3 +- ...ns-pull-requests-against-deploy-branch.mdx | 29 +++++++++++++++++++ 2 files changed, 31 insertions(+), 1 deletion(-) create mode 100644 help-center/agent-opens-pull-requests-against-deploy-branch.mdx diff --git a/docs.json b/docs.json index a34f823acb..ad6f69b303 100644 --- a/docs.json +++ b/docs.json @@ -492,7 +492,8 @@ "help-center/register-external-mcp-server-in-discovery", "help-center/visitor-count-dropped-after-crawler-filtering", "help-center/migrate-from-confluence", - "help-center/migrate-docs-from-a-zip-export" + "help-center/migrate-docs-from-a-zip-export", + "help-center/agent-opens-pull-requests-against-deploy-branch" ] } ] diff --git a/help-center/agent-opens-pull-requests-against-deploy-branch.mdx b/help-center/agent-opens-pull-requests-against-deploy-branch.mdx new file mode 100644 index 0000000000..500cabde9c --- /dev/null +++ b/help-center/agent-opens-pull-requests-against-deploy-branch.mdx @@ -0,0 +1,29 @@ +--- +title: "Agent and automation pull requests open against the deploy branch" +description: "Why the Mintlify agent and automations open pull requests against your deploy branch, and how to send changes to a different branch." +keywords: ["agent pull request base branch", "automation opens PR into main", "agent PR targets main", "change agent base branch", "automation base branch", "staging branch for agent"] +--- + +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](/agent/slack) for the Slack flow and [Choose how the agent publishes changes](/agent/index#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](https://app.mintlify.com/settings/deployment/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](/automations/manage#update-mode). + +## Related settings + +- [Choose how the agent publishes changes](/agent/index#choose-how-the-agent-publishes-changes) — pull request vs. direct push, and how branch protection interacts with each. +- [Git Settings](https://app.mintlify.com/settings/deployment/git-settings) — change the deploy branch or the docs subdirectory the deployment builds from. From fc8fb2f38b8874d28f88761bac776b2100495bc5 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 18 Sep 2026 16:22:21 +0000 Subject: [PATCH 2/2] docs: shorten title and add fr/es/zh translations for help center article --- es.json | 3 +- ...ns-pull-requests-against-deploy-branch.mdx | 35 +++++++++++++++++++ fr.json | 3 +- ...ns-pull-requests-against-deploy-branch.mdx | 35 +++++++++++++++++++ ...ns-pull-requests-against-deploy-branch.mdx | 2 +- zh.json | 3 +- ...ns-pull-requests-against-deploy-branch.mdx | 35 +++++++++++++++++++ 7 files changed, 112 insertions(+), 4 deletions(-) create mode 100644 es/help-center/agent-opens-pull-requests-against-deploy-branch.mdx create mode 100644 fr/help-center/agent-opens-pull-requests-against-deploy-branch.mdx create mode 100644 zh/help-center/agent-opens-pull-requests-against-deploy-branch.mdx diff --git a/es.json b/es.json index ffa5006de2..42a9164d43 100644 --- a/es.json +++ b/es.json @@ -470,7 +470,8 @@ "es/help-center/register-external-mcp-server-in-discovery", "es/help-center/visitor-count-dropped-after-crawler-filtering", "es/help-center/migrate-from-confluence", - "es/help-center/migrate-docs-from-a-zip-export" + "es/help-center/migrate-docs-from-a-zip-export", + "es/help-center/agent-opens-pull-requests-against-deploy-branch" ] } ] diff --git a/es/help-center/agent-opens-pull-requests-against-deploy-branch.mdx b/es/help-center/agent-opens-pull-requests-against-deploy-branch.mdx new file mode 100644 index 0000000000..d9a43ddfd8 --- /dev/null +++ b/es/help-center/agent-opens-pull-requests-against-deploy-branch.mdx @@ -0,0 +1,35 @@ +--- +title: "Los PR del agente se abren contra tu rama de despliegue" +description: "Por qué el agente de Mintlify y las automatizaciones abren solicitudes de extracción contra tu rama de despliegue y cómo enviar cambios a otra rama." +keywords: ["agent pull request base branch", "automation opens PR into main", "agent PR targets main", "change agent base branch", "automation base branch", "staging branch for agent"] +--- + +Cuando el agente de Mintlify o una automatización abre una solicitud de extracción, se dirige a la rama de despliegue configurada para tu proyecto (normalmente `main`). Es la rama desde la que Mintlify construye tu sitio en producción, por lo que los PR aterrizan allí por defecto y se publican al fusionarse. + +Si quieres que los cambios vayan a otro lugar, el mecanismo depende de cómo se haya iniciado la ejecución. + +
+ ## Ejecuciones del agente en Slack, el editor o el panel +
+ +Para una única ejecución del agente, indica la rama que quieres en el propio prompt. El agente crea la solicitud de extracción contra la rama que indiques, o envía los commits directamente a ella cuando ya existe. Por ejemplo: + +- "Abre el PR contra la rama `staging`." +- "Envía estos commits a `docs-refresh`." + +Consulta [Enviar mensajes al agente](/es/agent/slack) para el flujo en Slack y [Elige cómo publica los cambios el agente](/es/agent/index#choose-how-the-agent-publishes-changes) para la configuración a nivel de espacio de trabajo que decide entre abrir un PR o enviar directamente a tu rama de despliegue. + +
+ ## Automatizaciones +
+ +Las automatizaciones siempre abren sus solicitudes de extracción contra la rama de despliegue. No hay ninguna opción por automatización para dirigirse a una rama base distinta. Si necesitas que el resultado de una automatización aterrice en una rama que no sea de producción, apunta el propio despliegue a esa rama en [Git Settings](https://app.mintlify.com/settings/deployment/git-settings), o utiliza un despliegue independiente para esa rama y ejecuta la automatización allí. + +Para evitar que los PR de las automatizaciones se fusionen sin revisión, establece el modo de actualización de la automatización en **Modify and wait for review** en su página de configuración. Consulta [Modo de actualización](/es/automations/manage#update-mode). + + + +- [Elige cómo publica los cambios el agente](/es/agent/index#choose-how-the-agent-publishes-changes): solicitud de extracción frente a push directo, y cómo interactúa la protección de ramas con cada opción. +- [Git Settings](https://app.mintlify.com/settings/deployment/git-settings): cambia la rama de despliegue o el subdirectorio de docs desde el que se construye el despliegue. diff --git a/fr.json b/fr.json index 998fad760c..ea311315ea 100644 --- a/fr.json +++ b/fr.json @@ -470,7 +470,8 @@ "fr/help-center/register-external-mcp-server-in-discovery", "fr/help-center/visitor-count-dropped-after-crawler-filtering", "fr/help-center/migrate-from-confluence", - "fr/help-center/migrate-docs-from-a-zip-export" + "fr/help-center/migrate-docs-from-a-zip-export", + "fr/help-center/agent-opens-pull-requests-against-deploy-branch" ] } ] diff --git a/fr/help-center/agent-opens-pull-requests-against-deploy-branch.mdx b/fr/help-center/agent-opens-pull-requests-against-deploy-branch.mdx new file mode 100644 index 0000000000..6f4328acbc --- /dev/null +++ b/fr/help-center/agent-opens-pull-requests-against-deploy-branch.mdx @@ -0,0 +1,35 @@ +--- +title: "Les PR de l'agent visent votre branche de déploiement" +description: "Pourquoi l'agent Mintlify et les automatisations ouvrent des pull requests sur votre branche de déploiement, et comment cibler une autre branche." +keywords: ["agent pull request base branch", "automation opens PR into main", "agent PR targets main", "change agent base branch", "automation base branch", "staging branch for agent"] +--- + +Lorsque l'agent Mintlify ou une automatisation ouvre une pull request, celle-ci vise la branche de déploiement configurée pour votre projet (généralement `main`). C'est la branche depuis laquelle Mintlify construit votre site en production, donc les PR y atterrissent par défaut et sont publiées à la fusion. + +Si vous souhaitez que les changements aillent ailleurs, le mécanisme dépend de la façon dont l'exécution a été lancée. + +
+ ## Exécutions de l'agent dans Slack, l'éditeur ou le tableau de bord +
+ +Pour une exécution ponctuelle de l'agent, indiquez la branche voulue directement dans le prompt. L'agent crée la pull request sur la branche indiquée, ou pousse les commits directement dessus si la branche existe déjà. Par exemple : + +- « Ouvre la PR sur la branche `staging`. » +- « Pousse ces commits sur `docs-refresh`. » + +Consultez [Envoyer des messages à l'agent](/fr/agent/slack) pour le flux Slack et [Choisir comment l'agent publie les changements](/fr/agent/index#choose-how-the-agent-publishes-changes) pour le paramètre au niveau de l'espace de travail qui décide entre ouvrir une PR et pousser directement sur votre branche de déploiement. + +
+ ## Automatisations +
+ +Les automatisations ouvrent toujours leurs pull requests sur la branche de déploiement. Il n'existe pas de paramètre par automatisation pour cibler une autre branche de base. Si vous avez besoin que la sortie d'une automatisation atterrisse sur une branche hors production, pointez le déploiement lui-même vers cette branche dans [Git Settings](https://app.mintlify.com/settings/deployment/git-settings), ou utilisez un déploiement distinct pour cette branche et exécutez l'automatisation dessus. + +Pour empêcher les PR d'automatisation d'être fusionnées sans revue, réglez le mode de mise à jour de l'automatisation sur **Modify and wait for review** dans sa page de configuration. Voir [Mode de mise à jour](/fr/automations/manage#update-mode). + + + +- [Choisir comment l'agent publie les changements](/fr/agent/index#choose-how-the-agent-publishes-changes) : pull request ou push direct, et comment la protection de branche interagit avec chaque option. +- [Git Settings](https://app.mintlify.com/settings/deployment/git-settings) : modifiez la branche de déploiement ou le sous-répertoire de docs depuis lequel le déploiement est construit. diff --git a/help-center/agent-opens-pull-requests-against-deploy-branch.mdx b/help-center/agent-opens-pull-requests-against-deploy-branch.mdx index 500cabde9c..980741b3ee 100644 --- a/help-center/agent-opens-pull-requests-against-deploy-branch.mdx +++ b/help-center/agent-opens-pull-requests-against-deploy-branch.mdx @@ -1,5 +1,5 @@ --- -title: "Agent and automation pull requests open against the deploy branch" +title: "Agent PRs open against your deploy branch" description: "Why the Mintlify agent and automations open pull requests against your deploy branch, and how to send changes to a different branch." keywords: ["agent pull request base branch", "automation opens PR into main", "agent PR targets main", "change agent base branch", "automation base branch", "staging branch for agent"] --- diff --git a/zh.json b/zh.json index 8003849bca..987705c481 100644 --- a/zh.json +++ b/zh.json @@ -470,7 +470,8 @@ "zh/help-center/register-external-mcp-server-in-discovery", "zh/help-center/visitor-count-dropped-after-crawler-filtering", "zh/help-center/migrate-from-confluence", - "zh/help-center/migrate-docs-from-a-zip-export" + "zh/help-center/migrate-docs-from-a-zip-export", + "zh/help-center/agent-opens-pull-requests-against-deploy-branch" ] } ] diff --git a/zh/help-center/agent-opens-pull-requests-against-deploy-branch.mdx b/zh/help-center/agent-opens-pull-requests-against-deploy-branch.mdx new file mode 100644 index 0000000000..578b2cdcbb --- /dev/null +++ b/zh/help-center/agent-opens-pull-requests-against-deploy-branch.mdx @@ -0,0 +1,35 @@ +--- +title: "代理的 PR 面向你的部署分支打开" +description: "为什么 Mintlify 代理和自动化会向你的部署分支打开拉取请求,以及如何将更改发送到其他分支。" +keywords: ["agent pull request base branch", "automation opens PR into main", "agent PR targets main", "change agent base branch", "automation base branch", "staging branch for agent"] +--- + +当 Mintlify 代理或自动化打开一个拉取请求时,它会面向为你的项目配置的部署分支(通常是 `main`)。Mintlify 从该分支构建你的正式站点,因此 PR 默认会落在这里,并在合并时发布。 + +如果你希望更改进入其他位置,具体做法取决于运行是如何启动的。 + +
+ ## 在 Slack、编辑器或仪表板中的代理运行 +
+ +对于单次代理运行,请在提示中指定你想要的分支。代理会针对你指定的分支创建拉取请求;如果该分支已存在,则直接向其推送提交。例如: + +- "针对 `staging` 分支打开 PR。" +- "把这些提交推送到 `docs-refresh`。" + +Slack 流程请参见[向代理发送消息](/zh/agent/slack);工作区级别的审阅流程设置(决定打开 PR 还是直接推送到部署分支)请参见[选择代理如何发布更改](/zh/agent/index#choose-how-the-agent-publishes-changes)。 + +
+ ## 自动化 +
+ +自动化始终面向部署分支打开拉取请求。没有针对单个自动化设置其他基础分支的选项。如果你需要自动化的输出落在非生产分支上,请在 [Git Settings](https://app.mintlify.com/settings/deployment/git-settings) 中将部署本身指向该分支,或为该分支使用单独的部署并在其中运行该自动化。 + +若要防止自动化 PR 未经审阅就合并,请在自动化的配置页面将其更新模式设置为 **Modify and wait for review**。参见[更新模式](/zh/automations/manage#update-mode)。 + + + +- [选择代理如何发布更改](/zh/agent/index#choose-how-the-agent-publishes-changes):拉取请求与直接推送的对比,以及分支保护如何与两者交互。 +- [Git Settings](https://app.mintlify.com/settings/deployment/git-settings):更改部署分支或部署构建所使用的 docs 子目录。