codecov.yml Reference
Changing your YAML?
Changing your YAML? A reminder to always validate your YAML before you deploy https://api.codecov.io/validate
Top-level sections used in codecov.yml
codecov
codecov:
token: "<some token here>"
bot: "codecov-io"
ci:
- "travis.org"
strict_yaml_branch: "yaml-config"
max_report_age: 24
disable_default_path_fixes: no
require_ci_to_pass: yes
notify:
after_n_builds: 2
wait_for_ci: yes
codecov.token
The repository upload token
- Type: String
- Default: N/A
codecov.bot
The username you want to use for Codecov operations
- Type: String
- Default: N/A
- More Info: https://docs.codecov.io/docs/team-bot
codecov.ci
Additional CI provider URLs you want Codecov to recognize.
- Type: Map
- Default: N/A
- More Info: https://docs.codecov.io/docs/detecting-ci-services
codecov.strict_yaml_branch
Specify a branch you want Codecov to always only read the YAML from
- Type: String
- Default: N/A
- More Info: https://docs.codecov.io/docs/codecov-yaml#section-restricting-changes
codecov.max_report_age
The age you want coverage reports to expire at, or if you want to disable this check. Expired reports will not be processed by codecov.
- Type: Int, String, Boolean
- Default: 12h
- More Info: https://docs.codecov.io/docs/codecov-yaml#section-expired-reports
codecov.disable_default_path_fixes
Should Codecov's default path fixes be disabled
- Type: Boolean
- Default: no
- More Info: https://docs.codecov.io/docs/fixing-paths
codecov.require_ci_to_pass
Should Codecov wait for all other statuses to pass before sending its status.
- Type: Boolean
- Default: yes
codecov.notify
codecov.notify.after_n_builds
How many uploaded reports Codecov should wait to receive before sending statuses
- Type: Int
- Default: 1
- More Info: https://docs.codecov.io/docs/notifications#section-preventing-notifications-until-after-n-builds
codecov.notify.wait_for_ci
Should Codecov wait for all CI statuses to complete before sending ours.
Note: Codecov considers all non-codecov statuses to be CI statuses
- Type: Boolean
- Default: yes
coverage
coverage:
precision: 2
round: down
range: "70...100"
notify:
# notification blocks. See: https://docs.codecov.io/docs/codecovyml-reference#section-coverage-notify
status:
project:
patch:
changes:
coverage.precision
What precision do you want the coverage value to be
- Type: Range(0,5)
- Default: 2
coverage.round
Which direction to you want to round the coverage value
- Type: One of 'down', 'up', 'nearest'
- Default: down
coverage.range
The value range where you want the value to be green
- Type: start...end
- Default: 70..100
- More Info: https://docs.codecov.io/docs/coverage-configuration#section-range
coverage.notify
The standard notification settings are shown below, but it is recommend to view https://docs.codecov.io/docs/notifications for more information.
<notification_provider>: #see: ttps://docs.codecov.io/docs/notifications
url: "https://hooks.example.com/hook/8675309"
branches':
- master
- dev
- staging
threshold': 1%
flags:
- backend
- frontend
base: "parent"
only_pulls: false
paths: "*/**/*"
Note that the following notification providers are supported and will need to be defined in the YAML (see Notifications):
- Gitter
- Hipchat
- IRC
- Slack
coverage.status
See: https://docs.codecov.io/docs/commit-status for more information
coverage:
status:
project:
default: # This can be anything, but it needs to exist as the name
# basic settings
target: auto
threshold: 5%
base: auto
# advanced settings
branches:
- master
if_ci_failed: error #success, failure, error, ignore
only_pulls: false
flags:
- frontend
paths:
- src/frontend
parsers
parsers:
javascript:
enable_partials: yes # default yes
v1:
include_full_missed_files: true # default false
gcov:
branch_detection:
conditional: yes
loop: yes
method: no
macro: no
parsers.javascript
Unknown
- Type: map
- More Info: https://docs.codecov.io/docs/node
parsers.v1
Unknown
- Type: map
- More Info: https://docs.codecov.io/docs/ruby
parsers.gcov
Controls how Codecov parses branch coverage in gcov reports. The coverage must exist in the uploaded report for us to parse it.
- Type: map
parsers:
gcov:
branch_detection:
conditional: yes
loop: yes
method: no
macro: no
parsers.go
Controls how Codecov parses partial coverage in Golang reports. The coverage must exist in the uploaded report for us to parse it.
- Type: map
parsers:
go:
partials_as_hits: true #false by default
ignore
- More info: https://docs.codecov.io/docs/ignoring-paths
ignore:
- "path/to/folder" # ignore folders and all its contents
- "test_*.rb" # wildcards accepted
- "**/*.py" # glob accepted
fixes
- More info: https://docs.codecov.io/docs/fixing-paths
fixes:
- "before/::after/" # move path e.g., "before/path" => "after/path"
- "::after/" # move root e.g., "path/" => "after/path/"
- "before/::" # reduce root e.g., "before/path/" => "path/"
flags
- More info: https://docs.codecov.io/docs/flags
flags:
projectA:
paths:
- projectA/src
carryforward: false #default -- false
projectB:
paths:
- projectB/src
carryforward: true
comment
comment:
layout: "reach, diff, flags, files"
behavior: default
require_changes: false # if true: only post the comment if coverage changes
github_checks (GitHub users only)
github_checks:
annotations: false
Codecov Cloud Report Archiving
- How to disable archiving - In your codecov.yml, set the following line to false as follows:
codecov:
archive:
uploads: false
annotations
Specify whether to use GitHub Checks annotations or normal statuses. GitHub Checks are enabled by default and can be modified on the top level in your codecov.yml.
- Type: Boolean
- Default: true
- More Info: GitHub Checks
Updated about 2 years ago