Update/revisit codecov integration/config
- Dominant language
- No language data
- Stars
- 28
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
In/for https://github.com/jazzband/roadies/issues/8 apparently a yaml for the organization was created: https://codecov.io/account/gh/jazzband/yaml
I think we should use the new integration via https://github.com/apps/codecov/installations/new/permissions?target_id=15129049 instead, and remove the project config, as it seems to affect all projects, and overrides the default config.
But it might also make sense to set a default config here, given that most projects do not like codecov comments for example.
The following might be good, but includes comments:
```yaml
coverage:
status:
project: yes
patch: yes
changes: yes
comment:
layout: "header, diff, flags"
behavior: default
require_changes: no
```
Ref: https://docs.codecov.io/docs/codecov-yaml
Ref: https://docs.codecov.io/docs/pull-request-comments
Contributor guide
Research direction
Review the organization YAML at the linked Codecov account and the proposed integration installation link, then compare them with the Codecov YAML and pull-request comment documentation. Decide whether the project config should be removed or replaced with the proposed defaults; done means the selected integration and comment behavior are documented and configured without unintended organization-wide overrides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100