Skip to content

Update workflow: Draft docs for new features #4420

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

Closed
mintlify-development wants to merge 1 commit into from
Closed

Update workflow: Draft docs for new features #4420

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
10 changes: 7 additions & 3 deletions .mintlify/workflows/draft-feature-docs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,20 @@ name: "Draft docs for new features"
on:
push:
- repo: "mintlify/server"
context:
- repo: "mintlify/docs"
slack_channels:
- id: "C09F421M918"
name: "404-roast"
- id: "C0ADGKY425T"
name: "ae-dinner-approve"
Copy link
Copy Markdown

@cursor cursor Bot Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

branch: main
- repo: "mintlify/mint"
branch: main
context:
- repo: "mintlify/docs"
notify:
slack:
channel_ids:
- C0AKYE83VV4
automerge: false
Copy link
Copy Markdown

@cursor cursor Bot Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
Fix in Cursor Fix in Web

Copy link
Copy Markdown

@cursor cursor Bot Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

---

Review the diff from the last merged PR in the triggering repository. Identify any new features, APIs, or other changes that require documentation.
Expand Down
Loading