Allowing only single fork per user/organization #829

Closed
opened 2025-11-02 03:38:04 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @lafriks on GitHub (Jun 20, 2017).

I think we should allow only single fork for every user/organization from single repository. At least I don't see point of having multiple forks for each user and PR anyway does not work with multiple forks for one user because of url limitation. It could be also source of bad practice that users are creating new forks just for PR instead of normal workflow with new branches.

GitHub also does allow only single fork, just as GitLab.

If that's seem ok, I could create PR for this.

Originally created by @lafriks on GitHub (Jun 20, 2017). I think we should allow only single fork for every user/organization from single repository. At least I don't see point of having multiple forks for each user and PR anyway does not work with multiple forks for one user because of url limitation. It could be also source of bad practice that users are creating new forks just for PR instead of normal workflow with new branches. GitHub also does allow only single fork, just as GitLab. If that's seem ok, I could create PR for this.
GiteaMirror added the type/enhancement label 2025-11-02 03:38:04 -06:00
Author
Owner

@lunny commented on GitHub (Jun 21, 2017):

@lafriks please do it.

@lunny commented on GitHub (Jun 21, 2017): @lafriks please do it.
Author
Owner

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

Let's move this to v1.3 at first

@lunny commented on GitHub (Jun 23, 2017): Let's move this to v1.3 at first
Author
Owner

@lafriks commented on GitHub (Jun 23, 2017):

Yes

@lafriks commented on GitHub (Jun 23, 2017): Yes
Author
Owner

@lunny commented on GitHub (Jul 26, 2017):

resolved by #2193

@lunny commented on GitHub (Jul 26, 2017): resolved by #2193
Author
Owner

@bard commented on GitHub (Aug 6, 2017):

Does this also make it impossible for an individual user to fork a project to multiple organizations?

I described a scenario where that is needed at https://github.com/gogits/gogs/issues/1791#issuecomment-278899979, switched to Gitea because it implemented the feature as noted by @lunny at https://github.com/gogits/gogs/issues/1791#issuecomment-278905982, and am currently using it.

@bard commented on GitHub (Aug 6, 2017): Does this also make it impossible for an individual user to fork a project to multiple organizations? I described a scenario where that is needed at https://github.com/gogits/gogs/issues/1791#issuecomment-278899979, switched to Gitea because it implemented the feature as noted by @lunny at https://github.com/gogits/gogs/issues/1791#issuecomment-278905982, and am currently using it.
Author
Owner

@lunny commented on GitHub (Aug 6, 2017):

Yes, I think @bard is right. @lafriks, user cannot fork him repo to an organization now.

@lunny commented on GitHub (Aug 6, 2017): Yes, I think @bard is right. @lafriks, user cannot fork him repo to an organization now.
Author
Owner

@bard commented on GitHub (Aug 13, 2017):

Any chance of the fork-to-organization capability staying? I'm using this workflow, if future releases containing #2193 aren't allowing it I should start figuring out a migration path...

@bard commented on GitHub (Aug 13, 2017): Any chance of the fork-to-organization capability staying? I'm using this workflow, if future releases containing #2193 aren't allowing it I should start figuring out a migration path...
Author
Owner

@lunny commented on GitHub (Aug 13, 2017):

I think we will fix this at some time.

@lunny commented on GitHub (Aug 13, 2017): I think we will fix this at some time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#829