-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Comments
I think it's not difficult, need some config option in app.ini. |
@lunny You mean existing options or new options (thus some code change) ? |
@jbsarrodie new options |
Would welcome some more |
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. |
Similar to that it could be useful to have a setting to use external issue trackers by default if possible (i.e. |
yes: gitea/custom/conf/app.example.ini Lines 54 to 60 in 5c0697a
|
[x]
):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
The text was updated successfully, but these errors were encountered: