You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "JooHyukKim (via GitHub)" <gi...@apache.org> on 2023/11/10 00:26:39 UTC
[I] Re-examine `Codecov Report` usage. [pulsar]
JooHyukKim opened a new issue, #21550:
URL: https://github.com/apache/pulsar/issues/21550
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Motivation
## Background
For every PR, we have **Codecov Report (commenter)**.
## Consideration
Do we actually make something out of codecov report? By refering to image above, you can tell it takes up alot of space, so I thought it may be time to re-examine the report usage to see....
- If it is worth to have it (take up a whole laptop screen) when looking at a Pull Request page, among other reviews and discussions.
- If we can isolate it somewhere else (in case we make use of it)
### Solution
_No response_
### Alternatives
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Re-examine `Codecov Report` usage. [pulsar]
Posted by "JooHyukKim (via GitHub)" <gi...@apache.org>.
JooHyukKim closed issue #21550: Re-examine `Codecov Report` usage.
URL: https://github.com/apache/pulsar/issues/21550
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org