Skip to content
Open
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
8 changes: 0 additions & 8 deletions deploy/ci.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,18 +14,10 @@ Use CI checks to lint your docs for errors and provide warnings before you deplo

To begin, follow the steps on the [GitHub](/deploy/github) page.

<Tip>
The Mintlify GitHub App only need access to the repository where your documentation content exists. We recommend only granting access to that repository only.
</Tip>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Test PR removes important CI check documentation

Medium Severity

The PR title "test docs del" indicates this is a test deletion, yet it removes substantive documentation that doesn't exist elsewhere. The removed content explains Warning vs Blocking CI check levels — critical information for users configuring checks. The Tip about GitHub App repository access is also removed. The Configuration section now references enabling checks but no longer explains the available severity levels. This leaves the double blank line at lines 20–21 as an additional artifact of the incomplete removal.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 06a67c1. Configure here.

## Configuration

Configure the CI checks enabled for a deployment by navigating to the [Add-ons](https://dashboard.mintlify.com/products/addons) page of your dashboard. Enable the checks that you want to run.

When enabling checks, you can choose to run them at a `Warning` or `Blocking` level.

- A `Warning` level check never provides a failure status, even if there is an error or suggestions.
- A `Blocking` level check provides a failure status if there is an error or suggestions.

## Available CI checks

Expand Down
Loading