Skip to content

Add Codecov configuration (80% patch coverage, informational) - #253

Closed
eedri wants to merge 1 commit into
konflux-ci:mainfrom
eedri:add-codecov-config-80pct
Closed

Add Codecov configuration (80% patch coverage, informational)#253
eedri wants to merge 1 commit into
konflux-ci:mainfrom
eedri:add-codecov-config-80pct

Conversation

@eedri

@eedri eedri commented Sep 6, 2026

Copy link
Copy Markdown

Summary

Add Codecov configuration to enable code coverage tracking for this repository.

Context

This repo has been identified as a core production repo for Konflux to be tracked for code coverage and approved by the repo maintainer or tech-lead.

The configuration is set to informational mode (advisory only) with an 80% patch coverage target, meaning:

  • Coverage reports will be posted on PRs
  • The check will not block merges if coverage falls below 80%
  • This provides visibility without disrupting current workflows

Configuration details

  • Patch coverage target: 80% (informational)
  • Project coverage target: auto (informational)
  • CI requirement: disabled (coverage check won't block on CI failures)
  • Comments: disabled (reduces PR noise)

Related

This repo has been identified as a core production repo for Konflux
to be tracked for code coverage.

Configuration is set to informational mode (advisory only) with 80%
patch coverage target. The check will not block PRs.

Related: KFLUXDP-1172
@eedri
eedri requested a review from a team as a code owner September 6, 2026 12:03
@qodo-app-for-konflux-ci

Copy link
Copy Markdown

PR Summary by Qodo

Configure informational Codecov coverage checks

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Adds repository-wide Codecov coverage tracking.
• Sets an informational 80% patch coverage target.
• Keeps coverage checks non-blocking and disables PR comments.
High-Level Assessment

A root-level codecov.yml is Codecov's standard repository configuration mechanism. Informational project and patch statuses provide coverage visibility without disrupting existing merge workflows, while disabling comments limits PR noise.

Files changed (1) +16 / -0

Other (1) +16 / -0
codecov.ymlAdd non-blocking Codecov coverage policy +16/-0

Add non-blocking Codecov coverage policy

• Configures automatic project coverage with a 1% threshold and an 80% patch target. Both statuses are informational, CI success is not required, and PR comments are disabled.

codecov.yml

@qodo-app-for-konflux-ci

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@chmeliik

chmeliik commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

We already closed this once: #202

@eedri

eedri commented Sep 7, 2026

Copy link
Copy Markdown
Author

@chmeliik then why this repo was mentioned again to be tracked as core konflux repo?
I took thist list from the sheet @Dannyb48 shared on https://redhat-internal.slack.com/archives/C02CTEB3MMF/p1787860579663929

@chmeliik

chmeliik commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

@chmeliik then why this repo was mentioned again to be tracked as core konflux repo?

It is a core Konflux repo. And it doesn't make sense to track code coverage for it, because there is no code.

@eedri

eedri commented Sep 7, 2026

Copy link
Copy Markdown
Author

I see, OK. does the other leading metrics tracked in the unified dashboard are relevant for it?

@eedri eedri closed this Sep 7, 2026
@chmeliik

chmeliik commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

I see, OK. does the other leading metrics tracked in the unified dashboard are relevant for it?

I'm not familiar with the unified dashboard. Is it the stuff like "PR cycle time" etc? If so, then they're likely about as relevant as they are for other repos.

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