I’m not sure what it’s doing for that time (booting, loading cache, and comparing new repo with previous one?), but the build log definitely doesn’t show any of the build steps happenning.
Also, looks like this is a known issue:
opened 11:21AM - 04 Jan 21 UTC
closed 03:30PM - 26 Feb 21 UTC
bug
blocked
area: documentation
internal team only
size: estimated XS
**Describe the bug**
[Netlify docsdevto](https://app.netlify.com/sites/docsde… vto/deploys) is built on every [github.com/forem/forem](https://github.com/forem/forem) PR and fails if there is no content change.
```
10:54:33 AM: No changes detected in base directory. Returning early from build.
10:54:33 AM: Failed during stage 'checking build content for changes': Canceled build due to no content change
10:54:33 AM: Finished processing build request in 19.336942253s
```
_snippet from master@[e41c995](https://github.com/forem/forem/commit/e41c9954d6dfa887de78229b47e33c44822caa47) build_
**To Reproduce**
- List of Netlify builds: https://app.netlify.com/sites/docsdevto/deploys
- Log of master@[e41c995](https://github.com/forem/forem/commit/e41c9954d6dfa887de78229b47e33c44822caa47) build: https://app.netlify.com/sites/docsdevto/deploys/5ff2e5c4d7e5dc0007293c9a
**Expected behavior**
While this is not an real issue (Netlify builds do suceed when changes are pushed) I am just thinking if the build status influence other parts of the system (I first noticed the README [Netlify tag](https://api.netlify.com/api/v1/badges/e5dbe779-7bca-4390-80b9-6e678b4806a3/deploy-status)).
Or open up a discussion about the possibilities of strategically building the docsdevto to reduce the no-content builds – or if it's worth the effort to change it.
Hi there,
My site is auto deployed when I make an update to my github repo. I found that whenever I make a change to files which don’t impact the content of my website (e.g. updating the repository .readme) the build is triggered, then cancelled because there was no change to the website content.
When that happens the status badge shows as failing, but it’s not failing - it was just automatically cancelled because there was no reason to do the deployment.
Is this a bug, or something that I’m…
Looks like I don’t need to create a file, there’s a config for this :
As a temporary fix, we are avoiding this by adding ignore = "/bin/false" to the [build] section of our netlify.toml, forcing the build to proceed even if there haven’t been any changes in the front end. This works for us because we don’t have a huge merge volume, but it wouldn’t work for a team with a larger number of merges because it would eat into their build minutes.
I’m going to mark this as resolved because there’s another active thread… but the issue is not ‘resolved’ for me
