Update workflow: Draft docs for new features

[mintlify-development]

Updates the workflow configuration at .mintlify/workflows/draft-feature-docs.md.

---

Note

Medium Risk
Edits workflow trigger/metadata and Slack channel configuration, which could change when the workflow runs or who gets notified if the YAML is misconfigured.

Overview
Updates the Draft docs for new features workflow configuration by moving/adding context for mintlify/docs and introducing explicit slack_channels definitions for additional channels.

Also adjusts the on.push repo/branch configuration and removes the automerge: false setting, potentially changing how the workflow is triggered and reported.

^{Written by Cursor Bugbot for commit 3f3d2b7. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Broken YAML: push triggers displaced by misplaced blocks

High Severity

The context: and slack_channels: blocks were inserted between - repo: "mintlify/server" and its branch: main property, breaking the on.push list structure. As a result, mintlify/server lost its branch: main filter (triggering on all branches), and mintlify/mint is now nested under slack_channels instead of on.push (so it won't trigger the workflow at all). Comparing to the identical structure in update-api-reference.md confirms the intended layout.

Additional Locations (1)

• .mintlify/workflows/draft-feature-docs.md#L4-L5

 

[cursor]

Suspicious slack channels appear accidentally committed

Medium Severity

A slack_channels top-level key with channels named "404-roast" and "ae-dinner-approve" was added, but no other workflow file in .mintlify/workflows/ uses a slack_channels key — they all use notify.slack.channel_ids. These channel names don't appear related to documentation drafting and look like test or debug data that was accidentally included.

 

[cursor]

Removed automerge: false may enable unreviewed merges

Medium Severity

The automerge: false setting was removed from the frontmatter. The closely analogous update-api-reference.md workflow (same triggers, same context repo) explicitly includes automerge: false. Without it, this workflow's PRs may be automatically merged without human review, which is a meaningful behavior change likely unintended given the other structural issues in this commit.