Add extra 'Projects' layer #1246

New Issue

GiteaMirror · 2025-11-02T03:54:01-06:00

GiteaMirror commented

2025-11-02 03:54:01 -06:00

Originally created by @tonk on GitHub (Nov 15, 2017).

Currently the Gitea server has 'two levels', the Organisation and Repository levels.

I very often work for an organisation, doing a project that contains multiple repositories.
Now I'm creating an Organisation for each project, but is not the way I really want this to go.

It would be (in my opinion) be way better to have three levels, Organisation, Project and Repository levels.

Originally created by @tonk on GitHub (Nov 15, 2017). Currently the Gitea server has 'two levels', the Organisation and Repository levels. I very often work for an organisation, doing a project that contains multiple repositories. Now I'm creating an Organisation for each project, but is not the way I really want this to go. It would be (in my opinion) be way better to have three levels, Organisation, Project and Repository levels.

GiteaMirror added the issue/duplicate label 2025-11-02 03:54:01 -06:00

GiteaMirror closed this issue

2025-11-02 03:54:01 -06:00

GiteaMirror commented

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

@lafriks commented on GitHub (Nov 15, 2017):

I think Projects could be some kind of meta layer that should not be under organization but so that existing repositories could be added to them like links. This way same repository could be reused in multiple projects and also project could contain repositories from multiple organizations

@lafriks commented on GitHub (Nov 15, 2017): I think Projects could be some kind of meta layer that should not be under organization but so that existing repositories could be added to them like links. This way same repository could be reused in multiple projects and also project could contain repositories from multiple organizations

GiteaMirror commented

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

@tonk commented on GitHub (Nov 15, 2017):

Agree. To be honest, I'm not hooked on names, like Project or implementation. So I don't mind which way some functionality like would be implemented.

As I don't code in Go (yet, first training next week :-)) I'm not able to really help getting it in.

@tonk commented on GitHub (Nov 15, 2017): Agree. To be honest, I'm not hooked on names, like Project or implementation. So I don't mind which way some functionality like would be implemented. As I don't code in Go (yet, first training next week :-)) I'm not able to really help getting it in.

GiteaMirror commented

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

@RyanSquared commented on GitHub (Feb 16, 2019):

Relevant? #363

@RyanSquared commented on GitHub (Feb 16, 2019): Relevant? #363

GiteaMirror commented

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

@lunny commented on GitHub (Feb 17, 2019):

duplicated with #363

@lunny commented on GitHub (Feb 17, 2019): duplicated with #363

GiteaMirror referenced this issue

2025-11-02 11:55:35 -06:00