-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Feature request: "Hide a comment" on Pull Requests and Issues #5262
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Comment already has a We just have to add a ResolveReason witch could be a int (enum) or varchar if answers can be customized ... TODOs:
|
hey @6543, can i have a knock at this? |
@segfult sure go on ! (ps: target will be v1.15.0 then so dont rush :) ) |
Hi @6543 , I'd like to work on this issue. Before I get started though, it looks like currently only PR comments are resolve-able, and issue comments are not. Would it cause problems to also make issue comments hide-able/resolve-able? |
yes this is a feature request for issue and pull, its about the "normal comments" :) and you can follow the hits I describe above to get the job done :) |
I was happy to see Gitea had a "Review" feature on Pull Requests similar to GitHub when I was trialling it as replacement for our current hosting, but I'm kinda-of missing the "Hide a comment" feature.
Our main use-case for this would be hiding both PR comments and Code comments that no longer apply (either as "Resolved" or "Outdated"), but it wouldn't hurt to include other options for a more complete experience (such as "Off-topic", "Spam" or "Abuse" for example; but need not limited to those reasons).
We got an external issue tracker, but I'm certain it would also make sense with the built-in tracker to apply to Issues.
Comments would be displayed similar to how GitHub handles it, allowing a reader to expand them if needed:
The text was updated successfully, but these errors were encountered: