All coverage uploads are made towards master
See original GitHub issueIssue Description
Uploading reports using this action results in the branch
query parameter being empty and so CodeCov assumes that the commit belongs to master
(even though it can’t find it in the dashboard)
This is causing my badge to show incorrect values because now it’s getting affected by coverage reports that are uploaded from other branches.
For now, I’ve stopped using the action and I’m instead using the bash uploader directly.
- name: Upload coverage
if: success()
run: bash <(curl -s https://codecov.io/bash) -t $TOKEN -B $REF
env:
TOKEN: "${{ secrets.CODECOV_TOKEN }}"
REF: "${{ github.ref }}"
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to Generate a Code Coverage Report with CodeCov and ...
You can upload code coverage data generated in your local file system to codecov and easily visualize the coverage report on different charts....
Read more >Master Uploader Instructions.indd - NationWide Disc
The NationWide Disc Master Uploader is a free tool you can use to upload files and create your master for duplication OR replication...
Read more >GitLab CI/CD artifacts reports types
The collected coverage fuzzing report uploads to GitLab as an artifact. GitLab can display the results of one or more reports in: The...
Read more >AS91 – Asset Master Upload. - SAP Blogs
2019 to 28.02.2019 will be posted in Ordinary Depreciation Posted. Enter Asset Class and Company code. Enter all details as per your requirement ......
Read more >What are LANDR's track upload guidelines?
LANDR is designed primarily for stereo mixdowns, but if you're looking to master mono tracks - we've got you covered too. If you're...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re also facing this issue and has created a lot of issues in our coverage tracking + checks in PRs.
I’ve opened this PR to try and fix this.
Can someone take a look please?
Hi all,
We released integration for GitHub Actions on our Bash uploader yesterday which includes automatic branch tracking. This should resolve the issues y’all have been having regarding all uploads being directed towards master. Uploads should now be correctly associated with the right branch.
Ib