[
https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711651#comment-17711651
]
Zili Chen commented on CURATOR-660:
-----------------------------------
I ever brought best practices somewhere else if that project needed it, and was
also rejected when they didn't think a build change was good for their project.
* https://github.com/cockroachdb/cockroach/pull/78694
* https://github.com/tikv/tikv/pull/11080
* https://github.com/apache/pulsar-client-node/pull/314
* https://issues.apache.org/jira/browse/RATIS-1795
So maybe another sponsor who is an active contributor is a good reason to
accept such changes. Said I never use {{merge-pr.py}}, but the original
contributor uses it, so it’s OK to keep it there.
> Enable code coverage reporting to SonarQube
> -------------------------------------------
>
> Key: CURATOR-660
> URL: https://issues.apache.org/jira/browse/CURATOR-660
> Project: Apache Curator
> Issue Type: Task
> Reporter: Dóra Horváth
> Assignee: Zili Chen
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Enable coverage report generation and publishing to SonarQube.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
