-
-
Notifications
You must be signed in to change notification settings - Fork 457
Support deleting outdated comments in github-pr-review reporter #1804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
return cbody | ||
} | ||
|
||
func buildMetaComment(fprint string, toolName string) string { | ||
func BuildMetaComment(fprint string, toolName string) string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[golint-circleci] reported by reviewdog 🐶
exported function BuildMetaComment should have comment or be unexported
@@ -1,4 +1,4 @@ | |||
Custom text for testing | |||
Custom text for testing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[custom-rdjson] reported by reviewdog 🐶
test comment for deleting outdated comment 2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is a reply, this outdated comment should not be deleted.
This reverts commit ac36097.
// Do not remove comment with replies. | ||
continue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be easier to understand that reviewdog create a reply like This review comment has been resolved.
if there is a outdated review comment with replies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I agree with you to some extent, but if we'll create a reply comment, then we need to check whether we already have the reviewdog reply or not to avoid posting duplicated replies.
It needs extra logic and maitainance cost. I prefer keeping it as-is, at least for now, unless we have a simple way to handle this problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: ICHINOSE Shogo <shogo82148@gmail.com>
return cbody | ||
} | ||
|
||
func buildMetaComment(fprint string, toolName string) string { | ||
func BuildMetaComment(fprint string, toolName string) string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[golint-circleci] reported by reviewdog 🐶
exported function BuildMetaComment should have comment or be unexported
This adds a quality-of-life change of closing outdated discussions: reviewdog/reviewdog#1804
This adds a quality-of-life change of closing outdated discussions: reviewdog/reviewdog#1804
Fix #568