codecov / codecov/codecov-action
Flag management in yaml not working
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 260
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 1
Description
https://docs.codecov.com/docs/flags#step-2-flag-management-in-yaml
I tried this configuration:
flag_management:
default_rules: # the rules that will be followed for any flag added, generally
carryforward: true
statuses:
- type: project
target: 90% # overall project/ repo coverage
- type: patch
target: 90%
individual_flags: # exceptions to the default rules above, stated flag by flag
- name: backend
paths:
- backend/
carryforward: true
- name: webapp
paths:
- webapp/
carryforward: true
and also this configuration:
flag_management:
default_rules: # the rules that will be followed for any flag added, generally
carryforward: true
statuses:
- type: project
target: 90% # overall project/ repo coverage
- type: patch
target: 90%
flags:
backend:
paths:
- backend/
webapp:
paths:
- webapp/
and both of them is not working and UI don't show any flags
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked flag-management documentation and compare its YAML examples with the two configurations reported here. Then trace how the GitHub Action passes flag configuration to Codecov and reproduce the missing flags; done means a valid configuration makes the backend and webapp flags appear in the Codecov UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100