GitHub user suryaprasanna added a comment to the discussion: Let's turn the codecov-commenter OFF
@vinothchandar +1 on disabling code coverage on PRs. Developers and maintainers can use commands such as /coverage etc to trigger the report on-demand if needed. For the long term, I have a slightly different proposal. I just created a proposal to introduce a GitHub Merge Queue for Hudi: Ref: https://github.com/apache/hudi/issues/19612 By using this setup we can move code coverage reporting from individual PR commits to the merge queue. The merge queue already validates the exact set of changes that is about to land by running CI against the latest master plus the queued changes. We can run code coverage as part of this validation as a non-blocking check. On individual PRs, we can instead rely on hudi-agent to review whether adequate tests have been added for the change. This also reduces Codecov noise: instead of generating coverage updates for every PR commit, coverage is generated only when the change reaches the merge queue, resulting in a single coverage report for the version that is actually about to land. This way, hudi-agent provides semantic feedback on test adequacy during review, while Codecov continues to provide objective runtime coverage information at the final integration stage. GitHub link: https://github.com/apache/hudi/discussions/18992#discussioncomment-17995965 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
