Stop Vercel from deploying the docs repo - #475
Closed
archandatta wants to merge 1 commit into
Closed
Conversation
The Vercel project for this repo is configured as a Next.js app, and this repo has no package.json at all, so every deployment fails at "No Next.js version detected" — on main and on every pull request. Docs are deployed by Mintlify, which is the check that actually reports whether a change is live. Turning deployments off at the repo level removes a permanently red check that every contributor has learned to ignore. The alternative is disconnecting the project in the Vercel dashboard, which does the same thing but isn't visible here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
Vercelcheck has been red on every docs PR and onmainfor as long as the status history goes back. It is not a broken change — it is a misconfigured project.From the build log:
This repo has no
package.jsonat all, and the Vercel project's framework preset is Next.js. There is nothing here fornext buildto build and never was. Docs are deployed by Mintlify, which is the check that actually tells you whether a change went live.vercel.jsonwithgit.deploymentEnabled: falsemakes the Git integration skip this repo, so no deployment is attempted and no check is posted.Why bother
A check that is always red is a check nobody reads. #471, #469 and #468 all merged with it failing. Removing it means the next genuinely-red check on a docs PR means something.
Alternative
Disconnecting the project in the Vercel dashboard does the same thing. This lives in the repo instead, where it is visible and revertible in review — pick whichever you prefer. If Kernel does intend to build this repo on Vercel eventually, the fix is a
package.jsonplus the right framework preset, not this file.