Skip to content

Agent skill sync with docs: sub-branch merges and live status #8344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ethanpalm merged 1 commit into from
Nov 7, 2026
Merged

Agent skill sync with docs: sub-branch merges and live status #8344

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion agent-context/context/skills/mintlify/reference/publishing-and-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ How changes reach the live site, how to answer "is this live", and how to review

## What is live

- Edits made through the Admin MCP server or the Mintlify editor are unpublished until they are published. On the deploy branch they are pending changes; on any other branch they reach the site when that branch's pull request is merged.
- Edits made through the Admin MCP server or the Mintlify editor are unpublished until they are published. On the deploy branch they are pending changes; on any other branch they reach the site when that branch's pull request is merged into the deploy branch. In the editor, a sub-branch's pull request can target another non-deploy branch (its parent); merging it into the parent changes nothing live until the parent merges into the deploy branch.
- Saving and publishing are different steps. The editor saves edits on its own; publishing commits them to git.
- To answer "is this live" or "why can't I see my change", check what is unpublished (`status` or `diff` on the branch), whether a publish succeeded, and whether its deploy finished (`deployment_status` with the `commitSha` from `publish`; the change is live only when `live` is `true`). Say what you know and how the user can make it live. Do not guess, and do not claim a change is live when it only reached another branch.

Expand Down
Loading