From c37e4a7615259aaeee1e3fa4ad536393137777c8 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Sat, 23 May 2026 00:53:27 +0000 Subject: [PATCH] docs: document scheduled source code workflow and multi-PR runs --- workflows/enable.mdx | 19 +++++++++++++++++++ workflows/manage.mdx | 6 ++++++ 2 files changed, 25 insertions(+) diff --git a/workflows/enable.mdx b/workflows/enable.mdx index a465adc8c..1b3475e19 100644 --- a/workflows/enable.mdx +++ b/workflows/enable.mdx @@ -74,6 +74,25 @@ You can change the target languages at any time by opening the workflow's settin After saving the workflow, click **Translate now** to run it on demand using the currently saved target languages. The workflow must be enabled to trigger a manual run. Manual runs do not affect the workflow's regular trigger. +## New feature updates + +The **New feature updates** workflow watches one or more source code repositories and proposes documentation changes that reflect what shipped. + +You can run this workflow two ways: + +- **On push** — The agent runs when a pull request merges to a watched repository and drafts updates for that change. +- **On a schedule** — The agent gathers pull requests merged to the watched repositories since the last run and drafts a combined set of updates. Use scheduled mode when you want a single batched review on a cadence instead of one pull request per code change. + +### Configure source repositories + +When you set the trigger to a schedule, the **Source repositories** field replaces the trigger repository selector. Add every repository whose merged pull requests should feed the run. You must select at least one source repository before you can save a scheduled workflow. + +Merged pull requests from these repositories are collected before each scheduled run. Repository activity does not trigger the workflow — the schedule does. + +### Updates always open for review + +This workflow always opens a pull request against your docs repository. It does not support automerge, so the **How should updates be applied?** option does not appear in the settings modal. Review and merge each proposed change in your Git host. + ## Improve docs from assistant chats The **Improve docs from assistant chats** workflow reviews recent trends in [assistant](/assistant/index) questions and opens targeted documentation updates that address gaps your users hit. diff --git a/workflows/manage.mdx b/workflows/manage.mdx index 0064a7580..3fed60f0f 100644 --- a/workflows/manage.mdx +++ b/workflows/manage.mdx @@ -30,3 +30,9 @@ Each workflow keeps a log of past runs, including the status and a summary of ch Workflow runs with the status filter menu open. Workflow runs with the status filter menu open. + +### Runs with multiple pull requests + +A single run can produce more than one pull request. For example, a scheduled [New feature updates](/workflows/enable#new-feature-updates) workflow that watches several source repositories may open a separate documentation pull request for each. + +When a run includes multiple pull requests, expand the run row to see every pull request the agent opened. Each entry shows its title, status, and source repository, and exposes its own **Merge** and **Close** actions so you can review them independently.