aw-was-here commented on code in PR #261: URL: https://github.com/apache/yetus/pull/261#discussion_r861078688
########## asf-site-src/source/documentation/in-progress/precommit/plugins/github.html.md: ########## @@ -41,8 +41,16 @@ None | `--github-api-url=<url>` | REST API URL (for GitHub Enterprise) | | `--github-base-url=<url>` | Non-REST API URL (for GitHub Enterprise) | | `--github-repo=<repo>` | `username/repository` identifier | +| `--github-status-use-htmlreport=<bool>` | Use htmlout for Github Status 'Details' link | | `--github-token=<token>` | Token used to perform read and write operations | +## HTML Details LInk + +By default, if Apache Yetus is under conditions when it would normally write a Github Status (e.g., Jenkins processing Review Comment: Correct. That PR isn't using the checks API. You can see in pretty much any Apache Hadoop PR that down at the bottom there is a 'Details' link for 'Apache Yetus'. That should now point to the HTML report instead of the Jenkins console post this 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
