Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Add codecov token #1373

Merged
merged 2 commits into from
Apr 9, 2024

Conversation

binbin-li
Copy link
Collaborator

Description

What this PR does / why we need it:

Add cocdecov tokenso that codecov CLI could upload reports. Currently we only have PR uploading reports which don't require the token. But once we want to display the coverage for the main/dev branches, it will be required.

https://docs.codecov.com/docs/frequently-asked-questions#where-is-the-repository-upload-token-found

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • Does the affected code have corresponding tests?
  • Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
  • Does this introduce breaking changes that would require an announcement or bumping the major version?
  • Do all new files have appropriate license header?

Post Merge Requirements

  • MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Copy link

codecov bot commented Apr 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (staging@49201e9). Click here to learn what that means.

Additional details and impacted files
@@            Coverage Diff             @@
##             staging    #1373   +/-   ##
==========================================
  Coverage           ?   65.14%           
==========================================
  Files              ?      104           
  Lines              ?     5440           
  Branches           ?        0           
==========================================
  Hits               ?     3544           
  Misses             ?     1538           
  Partials           ?      358           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@susanshi susanshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@binbin-li binbin-li enabled auto-merge (squash) April 9, 2024 06:33
@binbin-li binbin-li disabled auto-merge April 9, 2024 06:38
@binbin-li binbin-li merged commit 034f5ec into ratify-project:staging Apr 9, 2024
13 checks passed
binbin-li added a commit that referenced this pull request Apr 9, 2024
binbin-li added a commit that referenced this pull request Apr 9, 2024
binbin-li added a commit to binbin-li/ratify that referenced this pull request Apr 9, 2024
akashsinghal pushed a commit that referenced this pull request Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants