Skip to content

NO-JIRA: chore(ci): add client/ to codecov ignore list#8167

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
enxebre:codecov-ignore-client
Apr 6, 2026
Merged

NO-JIRA: chore(ci): add client/ to codecov ignore list#8167
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
enxebre:codecov-ignore-client

Conversation

@enxebre
Copy link
Copy Markdown
Member

@enxebre enxebre commented Apr 6, 2026

Summary

  • Adds client/** to the codecov ignore list in codecov.yml
  • The client/ directory contains generated client code that should not count toward coverage metrics

Test plan

  • Verify codecov reports no longer include files under client/

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated code coverage configuration to exclude coverage reporting for the client directory.

Note: This release contains no user-facing changes or feature updates.

The client/ directory contains generated code that should
not count toward code coverage metrics.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot
Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 6, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 4c45150b-7ef4-40ce-9c60-2e4fb3d79748

📥 Commits

Reviewing files that changed from the base of the PR and between bcf6ada and 6e41081.

📒 Files selected for processing (1)
  • codecov.yml

📝 Walkthrough

Walkthrough

This pull request modifies the codecov.yml configuration file to exclude the client directory from code coverage reporting. The change adds client/** to the root ignore patterns section, which prevents coverage metrics for all files within the client directory from being reported. This is a configuration-only change with no impact on exported or public entities, and consists of a single line addition.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 6, 2026
@openshift-ci openshift-ci bot requested review from csrwng and jparrill April 6, 2026 15:57
@enxebre enxebre changed the title chore(ci): add client/ to codecov ignore list NO-JIRA: chore(ci): add client/ to codecov ignore list Apr 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@enxebre: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

  • Adds client/** to the codecov ignore list in codecov.yml
  • The client/ directory contains generated client code that should not count toward coverage metrics

Test plan

  • Verify codecov reports no longer include files under client/

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 6, 2026
@bryan-cox
Copy link
Copy Markdown
Member

/area ci-tooling

Copy link
Copy Markdown
Contributor

@jparrill jparrill left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added area/ci-tooling Indicates the PR includes changes for CI or tooling and removed do-not-merge/needs-area labels Apr 6, 2026
Copy link
Copy Markdown
Member

@bryan-cox bryan-cox left a comment

Choose a reason for hiding this comment

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

/lgtm

@jparrill
Copy link
Copy Markdown
Contributor

jparrill commented Apr 6, 2026

/area ci-tooling

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

  • The changed files don't match any pipeline_run_if_changed patterns
  • All files match pipeline_skip_if_only_changed patterns
  • No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

@jparrill
Copy link
Copy Markdown
Contributor

jparrill commented Apr 6, 2026

/verified by test

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@jparrill: This PR has been marked as verified by test.

Details

In response to this:

/verified by test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox, enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 6, 2026

@enxebre: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 27.50%. Comparing base (bcf6ada) to head (6e41081).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8167   +/-   ##
=======================================
  Coverage   27.50%   27.50%           
=======================================
  Files        1096     1096           
  Lines      107277   107277           
=======================================
  Hits        29503    29503           
  Misses      75240    75240           
  Partials     2534     2534           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-merge-bot openshift-merge-bot bot merged commit a1e18b8 into openshift:main Apr 6, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ci-tooling Indicates the PR includes changes for CI or tooling jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants