We have a GitHub connected project. We manually deploy to both preview and production via the CLI, and thus we don’t want Vercel to run any deployments automatically.
Yet when a PR is made, Vercel reports that the deployment timed out. However, our manually triggered deployment via the CLI (via GH Actions) is clearly passing. Why is Vercel still attempting to create a deployment? It’s also preventing us from merging. Similar issues here and here.
There are a lot of config choices here that could result in overly restrictive build cancelations.
I would recommend setting git.deploymentEnabled option to false in the vercel.json config to turn off all automatic deployments. You may need to make a deployment to get the new config established, then I would expect that any future GitHub commits not to trigger an automatic deployment. You may also want to change the Ignored Build Step back to Automatic to avoid unintended canceled builds.
Thank you for the response; git.deploymentEnabled is indeed set to false as I mentioned in my original post. We have tried having Ignored Build Step be both Automatic and Don't build anything, which doesn’t seem to make a difference.
I’ve tried fixing the capitalization issue mentioned in the discussion you posted, by deleting our GitHub environments, updating the workflow, and pushing it to a PR. This resolved the “failing check” but the merge is still blocked:
Note here that Preview - Branch Tracking is set to Disabled.