Repository navigation
Conversation
--github-update-comment[=<key>] implies --github-write-comment, and updates the comment the token's user previously wrote with the same key instead of adding a new one on every run. The report is skipped when the PR head moved past the tested commit. Assisted-by: Claude Opus 5.5
Member
Author
|
Tested end to end against real GitHub on pan3793/yetus-comment-test#1, running
The marker does not show in the rendered comment. The stale-build skip is covered by |
Member
Author
|
cc @aw-was-here @ndimiduk, could you please take a look? The current Yetus report (post a new comment for each report) keeps spamming the PR and makes it too hard for reviewers to find the real review comment ... |
Member
|
ACK. I'll make time to take a look in the next couple days, if Allen doesn't beat me to it. |
Member
Author
|
friendly ping @ndimiduk ~ |
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
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.
https://issues.apache.org/jira/browse/YETUS-1280
--github-write-commentadds a new PR comment on every run.--github-update-comment[=<key>]implies it and updates the comment the token's user previously wrote with the same key instead.<!-- yetus-report:<key> -->and adds aTested commitrow.GET /user, orgithub-actions[bot]under GitHub Actions), skipping hidden ones, and PATCHes it. Lookup or PATCH failures fall back to POST.Tested with the new
github_update_comment.bats.Assisted-by: Claude Opus 5.5