Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ability to completely disable Issues, Pull Requests, Milestones #20960

Closed
lzrdblzzrd opened this issue Aug 25, 2022 · 3 comments · Fixed by #24189
Closed

Ability to completely disable Issues, Pull Requests, Milestones #20960

lzrdblzzrd opened this issue Aug 25, 2022 · 3 comments · Fixed by #24189
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@lzrdblzzrd
Copy link

Feature Description

In the config file, it is possible to disable the Stars function so that it is impossible to put stars to repositories.
It would be nice if it were possible to disable the functions specified in the title if you host your own Gitea and do not use these functions.

Screenshots

image
@lzrdblzzrd lzrdblzzrd added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Aug 25, 2022
@lzrdblzzrd lzrdblzzrd changed the title Возможность полностью выключить Issues, Pull Requests, Milestones Ability to completely disable Issues, Pull Requests, Milestones Aug 25, 2022
@andreas-bulling
Copy link

This would be great to have!

@dieselburner
Copy link

dieselburner commented Apr 18, 2023 •
edited
Loading

Duplicate of #4750? Also, some of the mentioned things can be disabled/enabled in project settings via web interface.

@lunny
Copy link
Member

lunny commented Apr 18, 2023

I think #8788 has resolved the problem but there are some bugs now.

@lunny lunny mentioned this issue Apr 18, 2023
Merged
lunny added a commit that referenced this issue May 6, 2023
@lunny @delvh @yp05327
Require at least one unit to be enabled (#24189)
e5a8ebc 
Don't remember why the previous decision that `Code` and `Release` are
non-disable units globally. Since now every unit include `Code` could be
disabled, maybe we should have a new rule that the repo should have at
least one unit. So any unit could be disabled.

Fixes #20960
Fixes #7525

---------

Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: yp05327 <576951401@qq.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Require at least one unit to be enabled lunny/gitea
4 participants
@lunny @andreas-bulling @dieselburner @lzrdblzzrd