Builds cancelled for a new branch due to "no content change"

I’ve recently noticed that builds are automatically cancelled when there are no content changes. Generally this is great, but I am now trying to deploy a new branch that is virtually identical to the master branch, and builds are being cancelled for this same reason. Build log:

1:58:52 PM: Build ready to start
1:58:54 PM: build-image version: 342853e31ef590be8195dfbea64bbc4657de7b6b
1:58:54 PM: build-image tag: v3.3.16
1:58:54 PM: buildbot version: 0ffb969a1fc5a7aa9d2a93dd77dd40a990576807
1:58:55 PM: Fetching cached dependencies
1:58:55 PM: Failed to fetch cache, continuing with build
1:58:55 PM: Starting to prepare the repo for build
1:58:55 PM: No cached dependencies found. Cloning fresh repo
1:58:55 PM: git clone
1:58:56 PM: Preparing Git Reference refs/heads/demo
1:58:58 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘web/public’ versus ‘public’ in the Netlify UI
1:58:58 PM: No changes detected in base directory. Returning early from build.
1:58:58 PM: Failed during stage ‘checking build content for changes’: Canceled build due to no content change
1:58:58 PM: Finished processing build request in 3.437775397s

URL for the project is

How can I force this branch to build without having to modify the source code?

Hi @stufinn and sorry to be slow to get back to you! The only way to force that build will be to create a custom ignore command as mentioned in the article I link below, which is at least changing one file in your source repo, even if not the source of the project itself. So you may find it easier to make a dummy commit inside of the base directory, not sure!

You should be able to get away with this in your netlify.toml file:

   ignore = "/bin/false"

this will cause the “skip the build?” check to always say “DON’T SKIP”. You can/should remove that setting once you’ve gotten once successful build, otherwise we’ll always-never skip builds :upside_down_face:

1 Like

Oops just saw your response now. Thank you!

1 Like