Allow projects to have more than one git repo #1601

New Issue

GiteaMirror · 2025-11-02T04:06:15-06:00

GiteaMirror commented

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

Originally created by @Madmorgan007 on GitHub (Mar 6, 2018).

Hi, at times it nice to have more than one git repo under a single project. I use git sub modules and I like to separate out code from icons, documents. TFS and VSTS online both offer this could you?

Originally created by @Madmorgan007 on GitHub (Mar 6, 2018). Hi, at times it nice to have more than one git repo under a single project. I use git sub modules and I like to separate out code from icons, documents. TFS and VSTS online both offer this could you?

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

GiteaMirror commented

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

@thehowl commented on GitHub (Mar 6, 2018):

Hey there: you can create an organization and keep all your repositories there (kind of like we do here on GitHub, we keep all the repositories under the go-gitea organisation). Does this fit your usecase?

@thehowl commented on GitHub (Mar 6, 2018): Hey there: you can create an organization and keep all your repositories there (kind of like we do here on GitHub, we keep all the repositories under the go-gitea organisation). Does this fit your usecase?

GiteaMirror commented

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

@thehowl commented on GitHub (Mar 6, 2018):

Or would you like the two repos to have the same issues and wiki and so on?

@thehowl commented on GitHub (Mar 6, 2018): Or would you like the two repos to have the same issues and wiki and so on?

GiteaMirror commented

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

@Madmorgan007 commented on GitHub (Mar 6, 2018):

I like the idea of having two repos in a project using the same issue board and wiki.

@Madmorgan007 commented on GitHub (Mar 6, 2018): I like the idea of having two repos in a project using the same issue board and wiki.

GiteaMirror commented

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

@sapk commented on GitHub (Mar 7, 2018):

I can recommend you the solution of @thehowl and you can use a "master" repo using git submodules referencing repositry inside an organization and setting the wiki and issue to external link that reference the master repo.

@sapk commented on GitHub (Mar 7, 2018): I can recommend you the solution of @thehowl and you can use a "master" repo using git submodules referencing repositry inside an organization and setting the wiki and issue to external link that reference the master repo.

GiteaMirror commented

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

@Madmorgan007 commented on GitHub (Mar 7, 2018):

@sapk that to me just sounds like extra work you got to create a new project for each repo and then point the issues and wikis to the master site, it's quicker is to just have more than one repo in the project. I have a project that has about 5 sub modules that would mean changing 10 URL's to point to one master project.

@Madmorgan007 commented on GitHub (Mar 7, 2018): @sapk that to me just sounds like extra work you got to create a new project for each repo and then point the issues and wikis to the master site, it's quicker is to just have more than one repo in the project. I have a project that has about 5 sub modules that would mean changing 10 URL's to point to one master project.

GiteaMirror commented

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

@rmannibucau commented on GitHub (Dec 9, 2022):

+1 for this feature, having a project at organisation level sounds like a not that bad compromise.

@rmannibucau commented on GitHub (Dec 9, 2022): +1 for this feature, having a project at organisation level sounds like a not that bad compromise.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1601