I think it’s odd this is not obvious to do, but the only way I have found to disable a project connected to a repo from auto building every commit is to go into the “ignore build” script, and type in a bash script that exit codes 0.
Ignored build settings: exit 0;
That’s it!
This needs to be added as a feature, because some of Vercel’s features are project-wide and can’t be tested separately from your main project.
For example, enabling Vercel Deployment Protection, which requires a login/password etc. applies to the whole project, meaning your CI builds will fail as you try to update each one with a bypass method.
Therefore, the only way to have a live site and a test site to test/work on CI bypasses is to create a second project connected to the same repo.
But what if you don’t want to double your builds for a moment? Then see above…
- You can also disconnect the repo, but you will lose branch specific env vars
- You can delete the project, I guess
Yuji Tomita 