From c9a4e86a5d266a552d5d576e82f67add0448eb50 Mon Sep 17 00:00:00 2001 From: N43527 Date: Sun, 4 Oct 2026 20:30:10 -0700 Subject: [PATCH 1/6] Add Azure Repos deployment guide --- deploy/azure-repos.mdx | 102 +++++++++++++++++++++++++++++++++++++++++ docs.json | 1 + 2 files changed, 103 insertions(+) create mode 100644 deploy/azure-repos.mdx diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx new file mode 100644 index 0000000000..3eaac3bf43 --- /dev/null +++ b/deploy/azure-repos.mdx @@ -0,0 +1,102 @@ +--- +title: "Azure Repos" +description: "Connect an Azure Repos repository to Mintlify for automatic deployments when you push to your deploy branch." +keywords: ["Azure Repos", "Azure DevOps", "personal access token", "service hooks", "automated deployments"] +--- + + + Azure Repos must be enabled for your organization. Contact support@mintlify.com to turn it on. + + +Mintlify connects to Azure Repos with a personal access token. After you connect a repository, Mintlify creates a service hook in your Azure DevOps project and deploys every change pushed to your deploy branch. + +Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com`. Azure DevOps Server, the web editor, preview deployments, the Slack agent, and automations do not support Azure Repos repositories. + +## Requirements + +- An Azure DevOps user with **Basic** access who is a **Project Administrator** of the project that contains your repository. Azure DevOps only lets project administrators create service hooks. +- Admin access to your Mintlify organization +- A `docs.json` file in your repository + +## Create a personal access token + + + + 1. In Azure DevOps, click **User settings** in the top-right corner. + 2. Select **Personal access tokens**, then click **New Token**. + + + - **Name**: Mintlify + - **Organization**: The organization that contains your repository. Do not select **All accessible organizations**. + - **Expiration**: Azure DevOps allows a maximum of one year. + - **Scopes**: Select **Custom defined**, then select **Read** under **Code**. + + Click **Create** and copy the token. Azure DevOps only shows the token once. + + + +## Set up a new Azure Repos connection + +When you open [Git Settings](https://app.mintlify.com/settings/project/git-settings) for the first time, a setup wizard guides you through connecting your repository. + + + + 1. On the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page, click **Connect to Azure Repos**. + 2. Click **Continue**. + + + If you currently host your content in a Mintlify-managed repository, download it as a zip file. Extract the zip contents and push the files to your Azure Repos repository. + + If your content is already in Azure Repos, click **Continue setup**. + + + Enter the following values: + + - **Repository URL**: The HTTPS URL from the **Clone** button in Azure Repos. For example, `https://dev.azure.com/acme/docs-project/_git/docs`. + - **Deploy branch**: The branch that publishes to your production documentation site, such as `main`. + - **Personal access token**: The token you created. + + + 1. If your `docs.json` file is in a subdirectory, enable **docs.json is in a subdirectory**. + 2. Enter the path to the directory that contains your `docs.json` file. For example, if your `docs.json` is in the `apps/docs/` directory, enter `apps/docs`. + + + 1. Click **Connect**. + 2. Confirm the change. Mintlify verifies that the token can read your repository and that the deploy branch exists, registers the service hook that triggers deployments, and starts your first deployment. + + + +To confirm the service hook, open your Azure DevOps project and go to **Project settings** > **Service hooks**. The Mintlify subscription appears as a **Web Hooks** subscription for **Code pushed**. + +## Switch an existing deployment to Azure Repos + +1. On the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page, select **Azure Repos** as the Git provider. +2. Enter the repository URL, deploy branch, personal access token, and content directory. +3. Click **Switch to Azure Repos**. + +## Update your token + +Personal access tokens expire. Before your token expires, create a new token, paste it into the **Personal access token** field in [Git Settings](https://app.mintlify.com/settings/project/git-settings), and click **Save**. + +To change only the deploy branch or content directory, leave the token field as is and click **Save**. + +## Troubleshooting + + + + The token is invalid, expired, or scoped to a different organization. Create a new token scoped to the organization that contains your repository. + + + Check that the token has the **Code (Read)** scope and that its owner has **Basic** access to the project. Users with **Stakeholder** access can't read repositories in private projects. + + + Add the token's owner to the project's **Project Administrators** group, or create the token as a user who is already a project administrator. + + + In Azure DevOps, go to **Project settings** > **Service hooks** and open the Mintlify subscription to check its delivery history. Confirm that you pushed to the deploy branch configured in Mintlify. + + + + + Mintlify does not remove the service hook when you switch to a different Git provider. Delete it in **Project settings** > **Service hooks**. + diff --git a/docs.json b/docs.json index d50b99efd3..4310b8635f 100644 --- a/docs.json +++ b/docs.json @@ -194,6 +194,7 @@ "deploy/ghes", "deploy/gitlab", "deploy/bitbucket", + "deploy/azure-repos", "deploy/preview-deployments", "deploy/rollbacks" ] From 47a5e85bbf6fce5a6ca56d88c08b84c10079db71 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 16 Oct 2026 02:40:11 +0000 Subject: [PATCH 2/6] docs: update Azure Repos guide for Entra sign-in, pickers, and editor support --- deploy/azure-repos.mdx | 101 +++++++++++++++++++++++------------------ 1 file changed, 58 insertions(+), 43 deletions(-) diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx index 3eaac3bf43..40db588519 100644 --- a/deploy/azure-repos.mdx +++ b/deploy/azure-repos.mdx @@ -1,39 +1,26 @@ --- title: "Azure Repos" -description: "Connect an Azure Repos repository to Mintlify for automatic deployments when you push to your deploy branch." -keywords: ["Azure Repos", "Azure DevOps", "personal access token", "service hooks", "automated deployments"] +description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments and web editor publishing." +keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments"] --- Azure Repos must be enabled for your organization. Contact support@mintlify.com to turn it on. -Mintlify connects to Azure Repos with a personal access token. After you connect a repository, Mintlify creates a service hook in your Azure DevOps project and deploys every change pushed to your deploy branch. +Mintlify connects to Azure Repos through Microsoft Entra ID. You sign in with your Microsoft account so Mintlify can verify which organizations, projects, and repositories you can access. Mintlify then uses the Mintlify app in your Entra tenant to read your repository, create service hooks, and deploy every change pushed to your deploy branch. -Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com`. Azure DevOps Server, the web editor, preview deployments, the Slack agent, and automations do not support Azure Repos repositories. +Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com` in organizations connected to Microsoft Entra ID. Azure DevOps Server, preview deployments, the Slack agent, and automations do not support Azure Repos repositories. ## Requirements -- An Azure DevOps user with **Basic** access who is a **Project Administrator** of the project that contains your repository. Azure DevOps only lets project administrators create service hooks. -- Admin access to your Mintlify organization -- A `docs.json` file in your repository - -## Create a personal access token - - - - 1. In Azure DevOps, click **User settings** in the top-right corner. - 2. Select **Personal access tokens**, then click **New Token**. - - - - **Name**: Mintlify - - **Organization**: The organization that contains your repository. Do not select **All accessible organizations**. - - **Expiration**: Azure DevOps allows a maximum of one year. - - **Scopes**: Select **Custom defined**, then select **Read** under **Code**. - - Click **Create** and copy the token. Azure DevOps only shows the token once. - - +- An Azure DevOps organization connected to Microsoft Entra ID. +- An Entra administrator who grants consent to the Mintlify app in your tenant. +- The Mintlify app added to your Azure DevOps organization with **Basic** access, and to the project that contains your repository. +- The Mintlify app in the project's **Project Administrators** group. Azure DevOps only lets project administrators create service hooks. +- A Microsoft account that can read the repository you want to connect. +- Admin access to your Mintlify organization. +- A `docs.json` file in your repository. ## Set up a new Azure Repos connection @@ -49,12 +36,19 @@ When you open [Git Settings](https://app.mintlify.com/settings/project/git-setti If your content is already in Azure Repos, click **Continue setup**. - - Enter the following values: + + 1. Click **Connect Microsoft**. + 2. Sign in with a Microsoft account that can access the repository you want to connect. + + After you sign in, Microsoft redirects you to your Mintlify Git settings. + + + Select the following values. Each list shows the resources your Microsoft account can access. - - **Repository URL**: The HTTPS URL from the **Clone** button in Azure Repos. For example, `https://dev.azure.com/acme/docs-project/_git/docs`. + - **Organization**: The Azure DevOps organization. For example, in `https://dev.azure.com/acme/docs-project/_git/docs`, `acme` is the organization. + - **Project**: The project that contains the repository, such as `docs-project`. + - **Repository**: The repository name, such as `docs`. - **Deploy branch**: The branch that publishes to your production documentation site, such as `main`. - - **Personal access token**: The token you created. 1. If your `docs.json` file is in a subdirectory, enable **docs.json is in a subdirectory**. @@ -62,41 +56,62 @@ When you open [Git Settings](https://app.mintlify.com/settings/project/git-setti 1. Click **Connect**. - 2. Confirm the change. Mintlify verifies that the token can read your repository and that the deploy branch exists, registers the service hook that triggers deployments, and starts your first deployment. + 2. Confirm the change. + + Mintlify verifies that your Microsoft account can read the repository and that the deploy branch exists. Mintlify then registers the service hooks that keep your site and the web editor in sync and starts your first deployment. -To confirm the service hook, open your Azure DevOps project and go to **Project settings** > **Service hooks**. The Mintlify subscription appears as a **Web Hooks** subscription for **Code pushed**. +To confirm the service hooks, open your Azure DevOps project and go to **Project settings** > **Service hooks**. Mintlify creates three **Web Hooks** subscriptions for the repository: **Code pushed**, **Pull request created**, and **Pull request updated**. ## Switch an existing deployment to Azure Repos 1. On the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page, select **Azure Repos** as the Git provider. -2. Enter the repository URL, deploy branch, personal access token, and content directory. -3. Click **Switch to Azure Repos**. +2. If you haven't connected a Microsoft account, click **Connect Microsoft** and sign in. +3. Select the organization, project, repository, and deploy branch, and enter a content directory if needed. +4. Click **Switch to Azure Repos**. + +## Change the connected Microsoft account + +Mintlify refreshes Microsoft credentials automatically, so you don't need to rotate tokens. To use a different account, open the **Microsoft connection** section on the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page and click **Change account**. -## Update your token +## Edit in the web editor -Personal access tokens expire. Before your token expires, create a new token, paste it into the **Personal access token** field in [Git Settings](https://app.mintlify.com/settings/project/git-settings), and click **Save**. +You can edit Azure Repos content in the [web editor](/editor). When you publish, Mintlify pushes a branch to Azure Repos and opens a pull request against your deploy branch. -To change only the deploy branch or content directory, leave the token field as is and click **Save**. +- Branches that you push to Azure Repos sync into the editor. +- Changes to pull requests in Azure Repos sync into the matching editor branch. +- When you delete a branch in Azure Repos, Mintlify removes it from the editor. +- If your deploy branch has blocking branch policies, such as required reviewers, publish through a pull request. ## Troubleshooting - - The token is invalid, expired, or scoped to a different organization. Create a new token scoped to the organization that contains your repository. + + Ask an Entra administrator in your tenant to grant consent to the Mintlify app, then connect the repository again. - - Check that the token has the **Code (Read)** scope and that its owner has **Basic** access to the project. Users with **Stakeholder** access can't read repositories in private projects. + + Mintlify only supports Azure DevOps organizations backed by Microsoft Entra ID. Connect your organization to your Entra tenant in Azure DevOps under **Organization settings** > **Microsoft Entra**, then try again. - - Add the token's owner to the project's **Project Administrators** group, or create the token as a user who is already a project administrator. + + The Mintlify app can't read the repository. Add the Mintlify app to your Azure DevOps organization with **Basic** access, and add it to the project that contains the repository. + + + Mintlify needs to create service hooks to deploy your changes automatically. Add the Mintlify app to the project's **Project Administrators** group, then connect the repository again. + + + The Microsoft account connected in Git Settings can't read the repository. Click **Change account** and sign in with an account that has access. Users with **Stakeholder** access can't read repositories in private projects. + + + Check that the branch exists in the repository and that the name matches exactly. - In Azure DevOps, go to **Project settings** > **Service hooks** and open the Mintlify subscription to check its delivery history. Confirm that you pushed to the deploy branch configured in Mintlify. + In Azure DevOps, go to **Project settings** > **Service hooks** and open the Mintlify subscriptions to check their delivery history. Confirm that you pushed to the deploy branch configured in Mintlify. + + If a subscription is disabled or missing, click **Save** in [Git Settings](https://app.mintlify.com/settings/project/git-settings). Mintlify replaces any subscription that isn't healthy. - Mintlify does not remove the service hook when you switch to a different Git provider. Delete it in **Project settings** > **Service hooks**. + Mintlify does not remove the service hooks when you switch to a different Git provider. Delete them in **Project settings** > **Service hooks**. From 72270c8eabdb7d87d4163027421a82741159fdc5 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Sun, 25 Oct 2026 18:48:48 -0700 Subject: [PATCH 3/6] docs: update Azure Repos guide for previews, Manage permissions, and Enterprise gating Co-Authored-By: Claude Opus 5.5 (1M context) --- .../config/vocabularies/Mintlify/accept.txt | 1 + deploy/azure-repos.mdx | 27 ++++++++++++------- 2 files changed, 19 insertions(+), 9 deletions(-) diff --git a/.vale/styles/config/vocabularies/Mintlify/accept.txt b/.vale/styles/config/vocabularies/Mintlify/accept.txt index 9a4911d0a5..cb7c6de2ad 100644 --- a/.vale/styles/config/vocabularies/Mintlify/accept.txt +++ b/.vale/styles/config/vocabularies/Mintlify/accept.txt @@ -44,6 +44,7 @@ autosav(e|es|ed|ing) AVIF AWS axios +Azure Repos (?i)backlinks? bearerAuth Bing diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx index 40db588519..199d2ad918 100644 --- a/deploy/azure-repos.mdx +++ b/deploy/azure-repos.mdx @@ -1,16 +1,16 @@ --- title: "Azure Repos" -description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments and web editor publishing." -keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments"] +description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, and web editor publishing." +keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments", "preview deployments"] --- - Azure Repos must be enabled for your organization. Contact support@mintlify.com to turn it on. + Azure Repos requires an [Enterprise plan](https://mintlify.com/pricing?ref=azure-repos). -Mintlify connects to Azure Repos through Microsoft Entra ID. You sign in with your Microsoft account so Mintlify can verify which organizations, projects, and repositories you can access. Mintlify then uses the Mintlify app in your Entra tenant to read your repository, create service hooks, and deploy every change pushed to your deploy branch. +Mintlify connects to Azure Repos through Microsoft Entra ID. You sign in with your Microsoft account so Mintlify can verify which organizations, projects, and repositories you can access. Mintlify then uses the Mintlify app in your Entra tenant to read your repository, create service hooks, deploy every change pushed to your deploy branch, and create preview deployments for pull requests. -Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com` in organizations connected to Microsoft Entra ID. Azure DevOps Server, preview deployments, the Slack agent, and automations do not support Azure Repos repositories. +Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com` in organizations connected to Microsoft Entra ID. Azure DevOps Server, the Slack agent, and automations do not support Azure Repos repositories. ## Requirements @@ -18,7 +18,7 @@ Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` o - An Entra administrator who grants consent to the Mintlify app in your tenant. - The Mintlify app added to your Azure DevOps organization with **Basic** access, and to the project that contains your repository. - The Mintlify app in the project's **Project Administrators** group. Azure DevOps only lets project administrators create service hooks. -- A Microsoft account that can read the repository you want to connect. +- A Microsoft account that is a project administrator or has **Manage permissions** on the repository you want to connect. - Admin access to your Mintlify organization. - A `docs.json` file in your repository. @@ -38,7 +38,7 @@ When you open [Git Settings](https://app.mintlify.com/settings/project/git-setti 1. Click **Connect Microsoft**. - 2. Sign in with a Microsoft account that can access the repository you want to connect. + 2. Sign in with a Microsoft account that is a project administrator or has **Manage permissions** on the repository you want to connect. After you sign in, Microsoft redirects you to your Mintlify Git settings. @@ -58,7 +58,7 @@ When you open [Git Settings](https://app.mintlify.com/settings/project/git-setti 1. Click **Connect**. 2. Confirm the change. - Mintlify verifies that your Microsoft account can read the repository and that the deploy branch exists. Mintlify then registers the service hooks that keep your site and the web editor in sync and starts your first deployment. + Mintlify verifies that your Microsoft account can manage the repository and that the deploy branch exists. Mintlify then registers the service hooks that keep your site and the web editor in sync and starts your first deployment. @@ -73,7 +73,9 @@ To confirm the service hooks, open your Azure DevOps project and go to **Project ## Change the connected Microsoft account -Mintlify refreshes Microsoft credentials automatically, so you don't need to rotate tokens. To use a different account, open the **Microsoft connection** section on the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page and click **Change account**. +Your whole Mintlify organization shares the Microsoft account in Git Settings, and only admins can change it. Mintlify refreshes Microsoft credentials automatically, so you don't need to rotate tokens. + +To use a different account, open the **Microsoft connection** section on the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page and click **Change account**. The new account must be a project administrator or have **Manage permissions** on the repository. ## Edit in the web editor @@ -84,6 +86,10 @@ You can edit Azure Repos content in the [web editor](/editor). When you publish, - When you delete a branch in Azure Repos, Mintlify removes it from the editor. - If your deploy branch has blocking branch policies, such as required reviewers, publish through a pull request. +## Preview deployments + +When you open a pull request against your deploy branch, Mintlify builds a [preview deployment](/deploy/preview-deployments) and links to it from a **Mintlify preview ready** status on the pull request. Mintlify rebuilds the preview when you push to the pull request's branch, and deletes it when you complete or abandon the pull request or delete the branch. + ## Troubleshooting @@ -102,6 +108,9 @@ You can edit Azure Repos content in the [web editor](/editor). When you publish, The Microsoft account connected in Git Settings can't read the repository. Click **Change account** and sign in with an account that has access. Users with **Stakeholder** access can't read repositories in private projects. + + The Microsoft account connected in Git Settings can read the repository but can't manage it. Click **Change account** and sign in with an account that is in the project's **Project Administrators** group or has **Manage permissions** on the repository. + Check that the branch exists in the repository and that the name matches exactly. From e50de6d07ec35e38b3c5ad0ad6a5c94ca80b04b4 Mon Sep 17 00:00:00 2001 From: N43527 Date: Tue, 27 Oct 2026 11:08:28 -0700 Subject: [PATCH 4/6] docs: note legacy Azure DevOps URLs and Slack agent support for Azure Repos --- deploy/azure-repos.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx index 199d2ad918..caf44a92ea 100644 --- a/deploy/azure-repos.mdx +++ b/deploy/azure-repos.mdx @@ -10,7 +10,7 @@ keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", Mintlify connects to Azure Repos through Microsoft Entra ID. You sign in with your Microsoft account so Mintlify can verify which organizations, projects, and repositories you can access. Mintlify then uses the Mintlify app in your Entra tenant to read your repository, create service hooks, deploy every change pushed to your deploy branch, and create preview deployments for pull requests. -Mintlify supports Azure DevOps Services repositories hosted on `dev.azure.com` or `*.visualstudio.com` in organizations connected to Microsoft Entra ID. Azure DevOps Server, the Slack agent, and automations do not support Azure Repos repositories. +Mintlify supports Azure DevOps Services organizations on `dev.azure.com`, including organizations that still use `*.visualstudio.com` URLs, that are connected to Microsoft Entra ID. Mintlify does not support Azure DevOps Server. ## Requirements @@ -90,6 +90,10 @@ You can edit Azure Repos content in the [web editor](/editor). When you publish, When you open a pull request against your deploy branch, Mintlify builds a [preview deployment](/deploy/preview-deployments) and links to it from a **Mintlify preview ready** status on the pull request. Mintlify rebuilds the preview when you push to the pull request's branch, and deletes it when you complete or abandon the pull request or delete the branch. +## Use the agent in Slack + +The [agent in Slack](/agent/slack) works with Azure Repos. When you ask it to update your content, it opens a pull request in your Azure Repos repository. + ## Troubleshooting From b1e775059275bead28a6e186fff53c0a205906e4 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Thu, 29 Oct 2026 19:31:41 -0700 Subject: [PATCH 5/6] docs: document Autopilot on Azure Repos Autopilot supports Azure Repos as of mintlify/server#9904. Add Azure Repos to the Autopilot prerequisites and integrations, note that it can't assign, request reviews, or respond to comments on Azure Repos pull requests, and add an Autopilot section to the Azure Repos page. Co-Authored-By: Claude Opus 5.5 --- autopilot.mdx | 23 ++++++++++++++++++++--- deploy/azure-repos.mdx | 12 ++++++++++-- 2 files changed, 30 insertions(+), 5 deletions(-) diff --git a/autopilot.mdx b/autopilot.mdx index b3d2edd432..7d0cd95434 100644 --- a/autopilot.mdx +++ b/autopilot.mdx @@ -22,9 +22,10 @@ To change what Autopilot works on and when it runs, [chat with Autopilot](#chat- ## Prerequisites -- A Mintlify project connected to a GitHub or GitLab repository. Autopilot supports gitlab.com and [self-hosted GitLab](/deploy/gitlab-self-hosted) instances. +- A Mintlify project connected to a GitHub, GitLab, or Azure Repos repository. Autopilot supports gitlab.com and [self-hosted GitLab](/deploy/gitlab-self-hosted) instances. - For GitHub: the [Mintlify GitHub App](/deploy/github) installed on your docs repository and on any source code repositories you want Autopilot to use. - For GitLab: your docs repository and any source code repositories you want Autopilot to use connected in the **GitLab OAuth** section of your [Git settings](https://app.mintlify.com/settings/project/git-settings). On GitLab, Autopilot opens merge requests instead of pull requests. +- For Azure Repos: your docs repository and any source code repositories you want Autopilot to use connected in your [Git settings](https://app.mintlify.com/settings/project/git-settings). See [Azure Repos](/deploy/azure-repos). ## Enable Autopilot @@ -67,6 +68,20 @@ Your documentation project is always included as required context for Autopilot, The **Additional projects** list only shows GitLab projects connected through GitLab OAuth. To add a project that is not listed, click **Add GitLab projects** at the bottom of the list to open your Git settings and connect it. +### Azure Repos repositories + +If your docs repository is on [Azure Repos](/deploy/azure-repos), the **Integrations** section shows an **Azure Repos** row instead of a **GitHub** row. + +To choose the repositories Autopilot uses as context: + +1. Click **Configure** in the **Azure Repos** row. +2. Under **Additional repositories**, select the source code repositories you want Autopilot to use. +3. Click **Save**. + +Your documentation repository is always included as required context for Autopilot, so you cannot remove it. + +The **Additional repositories** list only shows Azure Repos repositories connected to your Mintlify organization. To add a repository that is not listed, click **Add Azure DevOps repositories** at the bottom of the list to open your Git settings and connect it. + ### Slack and other integrations Click **Connect** in the **Slack** row so Autopilot can build context from conversations. If you disconnect Slack from the Autopilot page, it removes the Mintlify Slack app from your workspace for every product that uses it, including automations. @@ -95,6 +110,8 @@ If your team already writes launch docs on its own branch, Autopilot opens its p By default, Autopilot assigns each pull request to the teammate it identifies as the owner of the code that changed, requests their review, and notifies them about the pull request. To request reviews from more people, change who reviews changes, or change how Autopilot notifies someone, tell Autopilot in a chat. +Autopilot does not assign Azure Repos pull requests or request reviews on them. + If you [connect Slack](#slack-and-other-integrations) and Autopilot can match the reviewer to a Slack account, it sends them a direct message in Slack. Otherwise, it emails them. When Autopilot opens the first pull request for a feature launch, it emails the launch's owners together with whether the pull request is a draft, what happens next, and the related channels, projects, specs, and code pull requests it is following. @@ -121,9 +138,9 @@ When Autopilot picks up a comment or inline review comment, it reacts with 👀 Autopilot only responds to comments from people who own the repository, belong to the GitHub organization that owns it, are collaborators on it, or have write access to it. It ignores comments from bots and comments addressed to someone else, such as a question that @mentions a teammate. -Autopilot does not respond to comments on GitLab merge requests. To ask for changes to a merge request, send a message in its suggestion on the Autopilot page. +Autopilot does not respond to comments on GitLab merge requests or Azure Repos pull requests. To ask for changes, send a message in the suggestion on the Autopilot page. -If a pull request has merge conflicts or your branch protection rules block the merge, resolve it on GitHub. +If a pull request has merge conflicts or your branch protection rules block the merge, resolve it in your Git provider. ## Chat with Autopilot diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx index caf44a92ea..516607027b 100644 --- a/deploy/azure-repos.mdx +++ b/deploy/azure-repos.mdx @@ -1,7 +1,7 @@ --- title: "Azure Repos" -description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, and web editor publishing." -keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments", "preview deployments"] +description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, web editor publishing, and Autopilot." +keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments", "preview deployments", "Autopilot"] --- @@ -90,6 +90,14 @@ You can edit Azure Repos content in the [web editor](/editor). When you publish, When you open a pull request against your deploy branch, Mintlify builds a [preview deployment](/deploy/preview-deployments) and links to it from a **Mintlify preview ready** status on the pull request. Mintlify rebuilds the preview when you push to the pull request's branch, and deletes it when you complete or abandon the pull request or delete the branch. +## Use Autopilot + +[Autopilot](/autopilot) works with Azure Repos. It runs when code merges into connected repositories and opens pull requests in your Azure Repos repository. Accept or close its pull requests on the Autopilot page, or merge them in Azure Repos. + +To give Autopilot more context, connect your source code repositories in Git Settings, then select them in the **Azure Repos** row of the Autopilot page. See [Azure Repos repositories](/autopilot#azure-repos-repositories). + +On Azure Repos, Autopilot does not assign pull requests, request reviews, or respond to pull request comments. To ask for changes, send a message in the suggestion on the Autopilot page. + ## Use the agent in Slack The [agent in Slack](/agent/slack) works with Azure Repos. When you ask it to update your content, it opens a pull request in your Azure Repos repository. From 2f54e659a7dc5705beabdbded1905f30ed938400 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 30 Oct 2026 15:27:41 -0700 Subject: [PATCH 6/6] Apply batched suggestions from code review Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> --- deploy/azure-repos.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy/azure-repos.mdx b/deploy/azure-repos.mdx index 516607027b..8cc0095ac1 100644 --- a/deploy/azure-repos.mdx +++ b/deploy/azure-repos.mdx @@ -1,7 +1,7 @@ --- title: "Azure Repos" description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, web editor publishing, and Autopilot." -keywords: ["Azure Repos", "Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments", "preview deployments", "Autopilot"] +keywords: ["Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments"] --- @@ -73,7 +73,7 @@ To confirm the service hooks, open your Azure DevOps project and go to **Project ## Change the connected Microsoft account -Your whole Mintlify organization shares the Microsoft account in Git Settings, and only admins can change it. Mintlify refreshes Microsoft credentials automatically, so you don't need to rotate tokens. +Your entire Mintlify organization shares the Microsoft account in Git Settings, and only admins can change it. Mintlify refreshes Microsoft credentials automatically, so you don't need to rotate tokens. To use a different account, open the **Microsoft connection** section on the [Git Settings](https://app.mintlify.com/settings/project/git-settings) page and click **Change account**. The new account must be a project administrator or have **Manage permissions** on the repository.