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.

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

Is it possible to have Wiki, Issues and Pull Requests disabled by default for new repositories ? #4750

Closed
2 of 7 tasks
jbsarrodie opened this issue Aug 20, 2018 · 7 comments
Closed
2 of 7 tasks
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@jbsarrodie
Copy link

  • Gitea version (or commit ref): 1.5.0
  • Git version: 2.18.0.windows.1
  • Operating system: Windows
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Hi, First of all thank you all for the great work on Gitea. That's really good!

I'm using Gitea as part of a custom solution based on Archi and its collaboration plugin. In this context I'm defining a custom configuration and set of templates & locales.

I'd like to have Wiki, Issues and Pull Requests disabled by default for new repositories. In fact I'd like to even be able to disable some of them completely. Is there a way to do this through app.ini or other (maybe not documented) trick ?

For the moment I'm planning to hack templates, but that's not a good solution IMHO.

Regards,

JB

@lunny lunny added type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Aug 20, 2018
@lunny
Copy link
Member

lunny commented Aug 20, 2018

I think it's not difficult, need some config option in app.ini.

@jbsarrodie
Copy link
Author

@lunny You mean existing options or new options (thus some code change) ?

@lafriks
Copy link
Member

lafriks commented Aug 20, 2018

@jbsarrodie new options

@gsantner
Copy link

Would welcome some more app.ini options aswell, could work just as DEFAULT_ENABLE_TIMETRACKING do.
Always do disable Wiki and Issues on new repos and enable it when required. Especially when using gitea for much repo mirrors this just means more clicks :D. (I don't want users to create issues or something on mirrors e.g. ).

@andreas-h
Copy link

Sorry for hijacking this issue a bit -- please let me know if I should rather create a separate issue.

What I would really like is to be able to have PRs, Wiki and Issues disabled by default for forks only, and enabled by default otherwise. In our organisation, several people will work with their own copies i.e. forks of a repo, but we want to keep issues etc in the central repo.

@alexanderadam
Copy link

Similar to that it could be useful to have a setting to use external issue trackers by default if possible (i.e. https://github.com/go-gitea/gitea/issues).

@6543
Copy link
Member

6543 commented Sep 7, 2020

yes:

; Comma separated list of globally disabled repo units. Allowed values: repo.issues, repo.ext_issues, repo.pulls, repo.wiki, repo.ext_wiki
DISABLED_REPO_UNITS =
; Comma separated list of default repo units. Allowed values: repo.code, repo.releases, repo.issues, repo.pulls, repo.wiki, repo.projects.
; Note: Code and Releases can currently not be deactivated. If you specify default repo units you should still list them for future compatibility.
; External wiki and issue tracker can't be enabled by default as it requires additional settings.
; Disabled repo units will not be added to new repositories regardless if it is in the default list.
DEFAULT_REPO_UNITS = repo.code,repo.releases,repo.issues,repo.pulls,repo.wiki,repo.projects

@6543 6543 closed this as completed Sep 7, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

7 participants