chore: disable Vercel Git deployments - #25
Closed
adnanhq wants to merge 1 commit into
Closed
Conversation
The docs site moved from Docusaurus/Vercel to Mintlify in 27cbaeb, which removed vercel.json and the vercel-deploy workflow. The Vercel GitHub App is still connected to this repo, so every PR gets a "Vercel" commit status that fails on a build that no longer exists (see #24). Set git.deploymentEnabled to false so Vercel skips creating deployments for all branches, which stops the failing status. Mintlify's own deployment check is unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing — this was opened in error and is not needed. No changes were merged. |
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.
Problem
The docs site migrated from Docusaurus/Vercel to Mintlify in 27cbaeb, which deleted
vercel.jsonand.github/workflows/vercel-deploy.yml. But the Vercel GitHub App is still connected to this repo, so it keeps trying to build a project that no longer exists — every PR gets a redVercelcommit status (#24 is the latest example).Fix
Add a minimal
vercel.jsonsettinggit.deploymentEnabled: false, which tells Vercel to skip creating deployments for all branches. No deployment means noVercelstatus, so the false failure goes away.Safety notes
main, so theVercelstatus was never a required check — removing it cannot block merges.docs.oaknetwork.org) is served by Mintlify, not this Vercel project. This change only stops new Vercel deployments; it does not delete the project or take down any existing deployment.Mintlify Deploymentcheck andsecurity/snykare untouched.true) to restore Vercel deployments.Follow-up (needs org-owner / Vercel dashboard access)
This silences the bot but the app is still installed. To remove it entirely (including the
Vercel Preview Commentscheck context), either:oak-network/docsfrom repository access, orccp-rotocol, projectdocs): Settings → Git → Disconnect, or delete the now-unused project.Existing open PRs will still show the old failed status on their current head commit; it clears once they pick up a new commit containing this file (e.g. merge
mainin).