# Default: false not being respected for project coverage settings in Codecov.yml

**URL:** <https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150>\
**Category:** Support\
**Created:** [March 17, 2020, 8:33pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150 "2020-03-17T20:33:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjaminsnorris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/benjaminsnorris/32/556_2.png) [@benjaminsnorris](https://community.codecov.com/u/benjaminsnorris)\
**Post date:** [March 17, 2020, 8:33pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/1 "2020-03-17T20:33:18Z")

</div>

### Description

In our .codecov.yml, we are trying to split up the project to look at the app, the unit tests, and the UI tests separately. As you can see, we tried including `default: false` under the project, but we are still getting failures in the PR related to that.

### Repository

Private, but latest commit is [here](https://codecov.io/gh/octanner/culture-cloud-ios/commit/112d97238426fe143b95c9f14f15e8ee3dbdfd28).

### Versions

macOS 10.15, Safari 13.0, Codecov 1.1.6

### Additional Information

Entire .codecov.yml file contents:

```auto
coverage:
  status:
    project:
      default: false # disable the default status that measures entire project
      unitTests:
        target: 90
        paths: 
          - "culture-cloud-iosTests"
      uiTests:
        target: 90
        paths:
         - "culture-cloud-iosUITests"
      app:
        target: auto
        threshold: 2
        paths: 
          - "culture-cloud-ios"

ignore:
  - "culture-cloud-iosTests/Matchers.swift"
  - "culture-cloud-ios/ **/** /*_Previews.swift"

```

---

<div class="post-metadata">

**Author:** ![benjaminsnorris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/benjaminsnorris/32/556_2.png) [@benjaminsnorris](https://community.codecov.com/u/benjaminsnorris)\
**Post date:** [March 17, 2020, 9:24pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/2 "2020-03-17T21:24:08Z")

</div>

Hmm, maybe it just takes time. It seems to be showing up properly now.

---

<div class="post-metadata">

**Author:** ![jerrod](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/jerrod/32/41_2.png) [@jerrod](https://community.codecov.com/u/jerrod)\
**Post date:** [March 23, 2020, 5:08am UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/3 "2020-03-23T05:08:12Z")

</div>

@benjaminsnorris glad this is working correctly. Out of curiosity, roughly how long did it take? I’d like to investigate a little more.

---

<div class="post-metadata">

**Author:** ![benjaminsnorris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/benjaminsnorris/32/556_2.png) [@benjaminsnorris](https://community.codecov.com/u/benjaminsnorris)\
**Post date:** [March 23, 2020, 3:33pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/4 "2020-03-23T15:33:46Z")

</div>

It seems as it was at least half an hour or more from when it originally posted. The first time I looked, the checks in the PR showed `codecov/project` and had the coverage amount, which was causing a failure. When I looked later, `codecov/project` was gone, and `codecov/project/app` was there and passing.

---

<div class="post-metadata">

**Author:** ![jerrod](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/jerrod/32/41_2.png) [@jerrod](https://community.codecov.com/u/jerrod)\
**Post date:** [March 27, 2020, 6:40pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/5 "2020-03-27T18:40:08Z")

</div>

Hey @benjaminsnorris – are you using the Flags feature?

> **[Flags](https://docs.codecov.com/docs/flags)**
>
> Group coverage reports based on type of tests or sub-projects/teams.

That may help further define these split tests.

Also, are you running your full coverage suite everytime? If not, you should consider using Carryforward Flags as well for partial test runs. [https://docs.codecov.io/docs/carryforward-flagshttps://docs.codecov.io/docs/carryforward-flags](https://docs.codecov.io/docs/carryforward-flagshttps://docs.codecov.io/docs/carryforward-flags)

---

<div class="post-metadata">

**Author:** ![benjaminsnorris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/benjaminsnorris/32/556_2.png) [@benjaminsnorris](https://community.codecov.com/u/benjaminsnorris)\
**Post date:** [April 2, 2020, 2:59pm UTC](https://community.codecov.com/t/default-false-not-being-respected-for-project-coverage-settings-in-codecov-yml/1150/6 "2020-04-02T14:59:27Z")

</div>

Thanks @jerrod. We are not using Flags right now, so we will look into that.

And we are running the full coverage suite every time as of now.