# "No Config Found" builds marked as Failed

**URL:** <https://discuss.circleci.com/t/no-config-found-builds-marked-as-failed/24912>\
**Category:** Bug Reports\
**Created:** [September 5, 2018, 2:17pm UTC](https://discuss.circleci.com/t/no-config-found-builds-marked-as-failed/24912 "2018-09-05T14:17:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gionn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gionn/32/15250_2.png) [@gionn](https://discuss.circleci.com/u/gionn)\
**Post date:** [September 5, 2018, 2:17pm UTC](https://discuss.circleci.com/t/no-config-found-builds-marked-as-failed/24912/1 "2018-09-05T14:17:24Z")

</div>

In this moment a push to a branch without a config.yml will lead to an error message, but IMHO it should be something less fatal (e.g. Skipped). I have a bunch of repositories with gh-pages branch that always shows as failed with very low interest.

```auto
#!/bin/sh -eo pipefail
# No configuration was found in your project. Please refer to https://circleci.com/docs/2.0/ to get started with your configuration.
false

Exited with code 1

```

---

<div class="post-metadata">

**Author:** ![marc](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/marc/32/835_2.png) [@marc](https://discuss.circleci.com/u/marc)\
**Post date:** [September 5, 2018, 2:24pm UTC](https://discuss.circleci.com/t/no-config-found-builds-marked-as-failed/24912/2 "2018-09-05T14:24:21Z")

</div>

If you add `[ci skip]` to the commit message on your GH-pages branch, no build will execute. This is what we usually do internally for gh-pages branches.