[
https://issues.apache.org/jira/browse/YETUS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195838#comment-15195838
]
Karthik Kambatla commented on YETUS-333:
----------------------------------------
Any 0s and -1s should definitely be reported on the JIRA. The +1s could be
hidden. And, it makes sense to include a link to the console that has the full
output.
bq. Someone I discussed this with a few months ago said, effectively: "I want
to see the long output for my own patches but not for anyone else's." Haha.
That is funny. In my case, my observations are purely based on a JIRA I am
contributing to.
> Shorter comments for pre-commit builds only highlighting areas of concern
> -------------------------------------------------------------------------
>
> Key: YETUS-333
> URL: https://issues.apache.org/jira/browse/YETUS-333
> Project: Yetus
> Issue Type: Improvement
> Reporter: Karthik Kambatla
>
> YETUS is pretty comprehensive in the pre-commit checks it runs. As we add
> more checks, the comments themselves become fairly long. In the interest of
> keeping the JIRA scrolls short, it might help to have shorter comments that
> highlight any concerning areas along with a link to the comprehensive
> checklist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
