Feature request: "Hide a comment" on Pull Requests and Issues #2484

New Issue

GiteaMirror · 2025-11-02T04:38:05-06:00

GiteaMirror commented

2025-11-02 04:38:05 -06:00

Originally created by @BhaaLseN on GitHub (Nov 3, 2018).

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:

Originally created by @BhaaLseN on GitHub (Nov 3, 2018). 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"](https://help.github.com/articles/managing-disruptive-comments/#hiding-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: ![hidden-comment](https://user-images.githubusercontent.com/826052/47952039-89b99080-df69-11e8-8ecf-a61667c9da53.png)

GiteaMirror added the topic/moderation issue/confirmed type/feature labels 2025-11-02 04:38:05 -06:00

GiteaMirror commented

2025-11-02 04:38:06 -06:00

@stale[bot] commented on GitHub (Jan 4, 2019):

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.

@stale[bot] commented on GitHub (Jan 4, 2019): 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.

GiteaMirror commented

2025-11-02 04:38:06 -06:00

@6543 commented on GitHub (Oct 31, 2020):

Comment already has a ResolveDoerID field.

We just have to add a ResolveReason witch could be a int (enum) or varchar if answers can be customized ...

TODOs:

extend struct [Go]
add action (similar to edit) for hide/unhide [Go]
update template to get menue and hide if set [HTML]
add smal migration based on struct update [ Go]

@6543 commented on GitHub (Oct 31, 2020): Comment already has a `ResolveDoerID` field. We just have to add a ResolveReason witch could be a int (enum) or varchar if answers can be customized ... TODOs: * [ ] extend struct [Go] * [ ] add action (similar to edit) for hide/unhide [Go] * [ ] update template to get menue and hide if set [HTML] * [ ] add smal migration based on struct update [ Go]

GiteaMirror commented

2025-11-02 04:38:06 -06:00

@radiohertz commented on GitHub (Feb 3, 2021):

hey @6543, can i have a knock at this?

@radiohertz commented on GitHub (Feb 3, 2021): hey @6543, can i have a knock at this?

GiteaMirror commented

2025-11-02 04:38:06 -06:00

@6543 commented on GitHub (Feb 3, 2021):

@segfult sure go on ! (ps: target will be v1.15.0 then so dont rush :) )

@6543 commented on GitHub (Feb 3, 2021): @segfult sure go on ! (ps: target will be v1.15.0 then so dont rush :) )

GiteaMirror commented

2025-11-02 04:38:07 -06:00

@jpjamipark commented on GitHub (Dec 3, 2021):

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?

@jpjamipark commented on GitHub (Dec 3, 2021): 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?

GiteaMirror commented

2025-11-02 04:38:07 -06:00

@6543 commented on GitHub (Dec 3, 2021):

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 :)

@6543 commented on GitHub (Dec 3, 2021): 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 :)

GiteaMirror referenced this issue

2025-11-02 12:10:19 -06:00

[PR #2484] [MERGED] Allow changing integration test database connection using env variables #16424

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2484