Update from support feedback: agent PR base branch help center article - #7412
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a help center article explaining that the agent and automations open pull requests against the configured deploy branch, and how to send single-run agent changes to a different branch.
Changes
help-center/agent-opens-pull-requests-against-deploy-branch.mdxdocs.jsonScoped narrowly to what human-handled support threads asked. The monorepo preview-comment thread in this bucket was resolved by the AI support assistant, so it was excluded per workflow guidance; existing pages (
/deploy/monorepo,/deploy/github,/agent/slack) already cover subdirectory config and prompting the agent to target a specific branch, so no changes were needed there.Support context
Note
Low Risk
Documentation and navigation JSON only; no product or runtime code changes.
Overview
Adds a help center article (
agent-opens-pull-requests-against-deploy-branch) in English plus es, fr, and zh translations, driven by support questions about agent and automation PRs targetingmain.The article explains that PRs default to the configured deploy branch, that one-off agent runs can name another branch in the prompt, and that automations always use the deploy branch unless you change Git Settings or use a separate deployment. It links to existing agent, automation, and Git Settings docs.
Navigation in
docs.jsonand each locale config registers the new page under the hidden Help center group so it is searchable.Reviewed by Cursor Bugbot for commit fc8fb2f. Bugbot is set up for automated code reviews on this repo. Configure here.