-
-
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
Add config options to hide issue events #17414
Conversation
Adds a config option `HIDE_ISSUE_EVENTS` to hide most issue events (changed labels, milestones, projects...) on the issue detail page. If this is true, only the following events (comment types) are shown: * plain comments * closed/reopned/merged * reviews
This comment has been minimized.
This comment has been minimized.
I think we should group these events into one line, instead of hiding them. GitHub does a good example. == Update: I just found that the grouping feature had been implemented. In my opinion, we should not use a global setting option to hide some events, it brings divergences in future, some one wants to hide this, some one else wants to hide others. |
@wxiaoguang if you take a look at the linked issue, you'll find this comment:
|
Why not instead of adding additional app setting just make it as user preference? (There was already PR to move user settings to new table so it should not be too hard to add new setting) |
I don't see why it could not be saved as json un user settings and implemented as checkboxes. My point is we already have way too many settings in app.ini and we should avoid adding more if that's possible imho |
Yes in general I agreed (also because not every user on an instance must like it if it's disabled) but I wasn't sure about the implementation, but I didn't thought about the way using a JSON, which is fine. So this is probably blocked by #16834 |
The only thing I'd like to know is to which page in the settings I'd add it, since it doesn't really fit one of the current pages |
imho the user settings page is missing an "appearance" tab. then we can move theme, language from the other (unrelated) tabs as well. |
I added a appearance tab in a separate branch, https://github.com/qwerty287/gitea/tree/appearance-prefs, and could open a PR for this if you like it :) |
Yes, please, do so |
A maintainer might add the |
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.
Just a few things, but overall it looks good to me.
Co-authored-by: Gusted <williamzijl7@hotmail.com>
Would anybody mind merging this? |
Of course only after I resolved conflicts... |
Merged and resolved conflicts, ready for merge. |
* giteaoffical/main: [skip ci] Updated translations via Crowdin Add config options to hide issue events (go-gitea#17414) Add js vendor directory to .gitattributes (go-gitea#18350)
* Add config option to hide issue events Adds a config option `HIDE_ISSUE_EVENTS` to hide most issue events (changed labels, milestones, projects...) on the issue detail page. If this is true, only the following events (comment types) are shown: * plain comments * closed/reopned/merged * reviews * Make configurable using a list * Add docs * Add missing newline * Fix merge issues * Allow changes per user settings * Fix lint * Rm old docs * Apply suggestions from code review * Use bitsets * Rm comment * fmt * Fix lint * Use variable/constant to provide key * fmt * fix lint * refactor * Add a prefix for user setting key * Add license comment * Add license comment * Update services/forms/user_form_hidden_comments.go Co-authored-by: Gusted <williamzijl7@hotmail.com> * check len == 0 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: 6543 <6543@obermui.de>
Adds config options to the user settings to hide most issue events (changed labels, milestones, projects...) on the issue detail page.
Closes #11418