Skip to content
Merged
Changes from all commits
Commits
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: 2 additions & 0 deletions autopilot.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@

Your documentation repository is always included as required context for Autopilot, so you cannot remove it.

The **Additional repositories** list only shows repositories where the Mintlify GitHub App is installed. To add a repository that is not listed, first install the GitHub App on it.

Check warning on line 53 in autopilot.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

autopilot.mdx#L53

In general, use active voice instead of passive voice ('is installed').

### Slack and other integrations

Expand All @@ -64,11 +64,13 @@

Autopilot usually commits its changes to a new branch and opens a pull request. It never pushes directly to your deploy branch or to the repository's default branch.

Autopilot creates its commits through the GitHub API, so GitHub signs them and shows them as **Verified**. Autopilot's commits work with branch protection rules that require signed commits.

Pull requests target your deploy branch by default. If your team merges changes into a different branch than the one your site deploys from, tell Autopilot in a chat, and it targets that branch instead.

### Feature launches

For a large feature launch, such as a feature that spans several pull requests or repositories, ships behind a flag or beta with a launch date, or needs several new pages, Autopilot tracks the launch instead of opening a one-off pull request. It can wait until the feature settles before drafting, then opens the docs pull request as a draft and keeps it current as more code merges. Autopilot marks the pull request ready for review once the code has merged or the launch date is set.

Check warning on line 73 in autopilot.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

autopilot.mdx#L73

In general, use active voice instead of passive voice ('is set').

If your team already writes launch docs on its own branch, Autopilot opens its pull request against that branch. To have Autopilot push commits directly to your team's launch branch instead, tell Autopilot in a chat.

Expand Down Expand Up @@ -108,15 +110,15 @@
- Ask when Autopilot runs and which repositories and integrations it uses.
- Tell Autopilot to have a specific teammate review a pull request.
- Ask Autopilot to run a weekly check for broken links.
- Ask Autopilot to check the docs when a new Linear issue is created.

Check warning on line 113 in autopilot.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

autopilot.mdx#L113

In general, use active voice instead of passive voice ('is created').

Chats require the editor or admin [role](/dashboard/roles). You cannot start a new chat while Autopilot is paused.

Check warning on line 115 in autopilot.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

autopilot.mdx#L115

In general, use active voice instead of passive voice ('is paused').

## Pause Autopilot

To pause Autopilot, switch off the toggle on the **Autopilot** card.

When you resume Autopilot, it builds context on changes that happened while it was paused, but it does not create updates for them.

Check warning on line 121 in autopilot.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

autopilot.mdx#L121

In general, use active voice instead of passive voice ('was paused').

### Automatic pauses

Expand Down
Loading