A way to disable the Code tab for a project, or make the Wiki the first tab. #4849

New Issue

GiteaMirror · 2025-11-02T06:04:52-06:00

GiteaMirror commented

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

Originally created by @lpar on GitHub (Feb 13, 2020).

Maybe I'm crazy, but I'd like to be able to use Gitea as a lightweight issue tracking system for projects which don't necessarily have source code in any meaningful sense, or where the source code isn't the first thing you'd want users to see.

How difficult would it be to have an option to disable the code tab completely, or failing that, an option to make the Wiki be the first tab and open by default on clicking through to the project?

Originally created by @lpar on GitHub (Feb 13, 2020). Maybe I'm crazy, but I'd like to be able to use Gitea as a lightweight issue tracking system for projects which don't necessarily have source code in any meaningful sense, or where the source code isn't the first thing you'd want users to see. How difficult would it be to have an option to disable the code tab completely, or failing that, an option to make the Wiki be the first tab and open by default on clicking through to the project?

GiteaMirror added the type/proposal label 2025-11-02 06:04:53 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

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

@guillep2k commented on GitHub (Feb 14, 2020):

Reordering the tabs can be probably accomplished by providing your own copy of templates/repo/header.tmpl. You must take the original file from the source, and place it inside your custom directory (check Customizing Gitea). Please make sure you use the version that matches your Gitea. In the previous example I've linked to v1.11.0 just because it's the current release.

@guillep2k commented on GitHub (Feb 14, 2020): Reordering the tabs can be probably accomplished by providing your own copy of `templates/repo/header.tmpl`. You must take the original file from [the source](https://github.com/go-gitea/gitea/blob/v1.11.0/templates/repo/header.tmpl), and place it inside your `custom` directory (check [Customizing Gitea](https://docs.gitea.io/en-us/customizing-gitea/)). Please make sure you use the version that matches your Gitea. In the previous example I've linked to `v1.11.0` just because it's the current release.

GiteaMirror commented

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

@lpar commented on GitHub (Feb 14, 2020):

Right, I don't want it like that for every project though.

@lpar commented on GitHub (Feb 14, 2020): Right, I don't want it like that for _every_ project though.

GiteaMirror commented

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

@guillep2k commented on GitHub (Feb 18, 2020):

As an idea, an {{if ...}} could be placed to change the tab order if a repository name begins with "tracker-", or when it has a certain topic (label).

I don't mean to put your request down, though. I too think it's a valid use case. I know however that doing that properly (disabling code) might require a lot of changes because Gitea assumes code is always enabled, and code handling code (ehem) is everywhere.

@guillep2k commented on GitHub (Feb 18, 2020): As an idea, an `{{if ...}}` could be placed to change the tab order if a repository name begins with "tracker-", or when it has a certain topic (label). I don't mean to put your request down, though. I too think it's a valid use case. I know however that doing that properly (disabling code) might require a lot of changes because Gitea assumes code is always enabled, and code handling code (ehem) is everywhere.

GiteaMirror commented

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

@lunny commented on GitHub (Feb 18, 2020):

Currently, if you create a repository on an orgnization and create a team with no code permission. That it is.
That means, it's not difficult to implement but need a PR.

@lunny commented on GitHub (Feb 18, 2020): Currently, if you create a repository on an orgnization and create a team with no code permission. That it is. That means, it's not difficult to implement but need a PR.

GiteaMirror commented

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

@yardenshoham commented on GitHub (May 14, 2023):

@lunny did you implement this?

@yardenshoham commented on GitHub (May 14, 2023): @lunny did you implement this?

GiteaMirror commented

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

@lunny commented on GitHub (May 14, 2023):

Yes

@lunny commented on GitHub (May 14, 2023): Yes

GiteaMirror referenced this issue

2025-11-02 13:51:15 -06:00