NUTCH-3208 GitHub Actions JUnit and Yetus workflows do not reliably post PR comments - #963
Open
lewismc wants to merge 1 commit into
Open
NUTCH-3208 GitHub Actions JUnit and Yetus workflows do not reliably post PR comments#963lewismc wants to merge 1 commit into
lewismc wants to merge 1 commit into
Conversation
…ost PR comments (yetus): post a sticky report from a workflow_run companion so fork PRs can comment. Find the existing comment with gh; generate markdown on pull_request only.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(yetus): post a sticky report from a
workflow_runcompanion so fork PRs can comment. Find the existing comment withgh; generate markdown onpull_requestonly.PR fixes part 2 of NUTCH-3208
Again, unfortunately, the GitHub workflow result cannot be properly validated unless it is merged into
masterand then the workflow is run on a new incoming PR...which is what I did in my local setup.