Skip to content

Skip Coverage Check when forks are updated#7177

Merged
weizhouapache merged 1 commit into
apache:mainfrom
jbampton:fix-codecov-on-forks
Feb 13, 2023
Merged

Skip Coverage Check when forks are updated#7177
weizhouapache merged 1 commit into
apache:mainfrom
jbampton:fix-codecov-on-forks

Conversation

@jbampton

@jbampton jbampton commented Feb 7, 2023

Copy link
Copy Markdown
Member

Description

This PR skips the coverage check instead of failing when forks are updated.

After this PR is merged and forks are updated it should skip the check.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

Shows the failing check

Screen Shot 2023-02-08 at 1 20 49 am

How Has This Been Tested?

@codecov

codecov Bot commented Feb 7, 2023

Copy link
Copy Markdown

Codecov Report

Merging #7177 (fc0d009) into main (b93608e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #7177   +/-   ##
=========================================
  Coverage     12.63%   12.63%           
  Complexity     8609     8609           
=========================================
  Files          2711     2711           
  Lines        255748   255748           
  Branches      39871    39871           
=========================================
  Hits          32303    32303           
  Misses       219347   219347           
  Partials       4098     4098           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@sonarqubecloud

sonarqubecloud Bot commented Feb 7, 2023

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@DaanHoogland

Copy link
Copy Markdown
Contributor

@jbampton why do we want this?
will it skip coverage checks on PRs when the fork they come from is updated?

@DaanHoogland DaanHoogland left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

code looks good, but I wonder ow this works on PRs

@weizhouapache

weizhouapache commented Feb 9, 2023

Copy link
Copy Markdown
Member

@jbampton why do we want this? will it skip coverage checks on PRs when the fork they come from is updated?

actually there is a line in the yaml file

on: [pull_request, push]

so this check is not performed on the github forks.

However, if you push to your own repository, the check will be performed.
in this case, you need to add codecov token in your project, and codecov should work.
you can look at my repo where codecov works. @jbampton
https://github.com/weizhouapache/cloudstack-new/actions/workflows/codecov.yml
if you want to disable the checks, you can just remove them as it is your own fork/repository.

@weizhouapache

weizhouapache commented Feb 9, 2023

Copy link
Copy Markdown
Member

in short, I am 0 on this PR. I did not see benefit/harmless for cloudstack project.

@jbampton can you add the check on other github actions (e.g. main-sonar-check.yml, ui.yml, ci.yml) as well ?

@weizhouapache weizhouapache merged commit dcf01f7 into apache:main Feb 13, 2023
@weizhouapache

Copy link
Copy Markdown
Member

in short, I am 0 on this PR. I did not see benefit/harmless for cloudstack project.

@jbampton can you add the check on other github actions (e.g. main-sonar-check.yml, ui.yml, ci.yml) as well ?

no worries. created a PR to follow up : #7199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants