Support multiple forks within the same organization #5613

Closed
opened 2025-11-02 06:30:55 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @flomontl on GitHub (Jun 22, 2020).

  • Gitea version (or commit ref): 1.12.0
  • Can you reproduce the bug at https://try.gitea.io:
    • [x ] Yes (provide example URL)

Description

This is not possible with GITea to fork a repo twice (or more) within the same organization.
Whereas it seems to be possible in GITLab:
https://gitlab.com/gitlab-org/gitlab-foss/-/issues/36268

Originally created by @flomontl on GitHub (Jun 22, 2020). - Gitea version (or commit ref): 1.12.0 - Can you reproduce the bug at https://try.gitea.io: - [x ] Yes (provide example URL) ## Description This is not possible with GITea to fork a repo twice (or more) within the same organization. Whereas it seems to be possible in GITLab: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/36268
GiteaMirror added the issue/stale label 2025-11-02 06:30:55 -06:00
Author
Owner

@lunny commented on GitHub (Jun 23, 2020):

I don't think github will allow you do that.

@lunny commented on GitHub (Jun 23, 2020): I don't think github will allow you do that.
Author
Owner

@6543 commented on GitHub (Jun 23, 2020):

I dont see an good usecase in this

@6543 commented on GitHub (Jun 23, 2020): I dont see an good usecase in this
Author
Owner

@flomontl commented on GitHub (Jun 23, 2020):

@lunny , I read this link: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/36268

@flomontl commented on GitHub (Jun 23, 2020): @lunny , I read this link: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/36268
Author
Owner

@stale[bot] commented on GitHub (Aug 22, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 22, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5613