Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allowing only single fork per user/organization #2019

Closed
lafriks opened this issue Jun 20, 2017 · 8 comments
Closed

Allowing only single fork per user/organization #2019

lafriks opened this issue Jun 20, 2017 · 8 comments
Labels
type/enhancement An improvement of existing functionality
Milestone

Comments

@lafriks
Copy link
Member

lafriks commented 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.

@lunny lunny added the type/enhancement An improvement of existing functionality label Jun 21, 2017
@lunny lunny added this to the 1.2.0 milestone Jun 21, 2017
@lunny
Copy link
Member

lunny commented Jun 21, 2017

@lafriks please do it.

@lunny
Copy link
Member

lunny commented Jun 23, 2017

Let's move this to v1.3 at first

@lunny lunny modified the milestones: 1.3.0, 1.2.0 Jun 23, 2017
@lafriks
Copy link
Member Author

lafriks commented Jun 23, 2017

Yes

@lunny
Copy link
Member

lunny commented Jul 26, 2017

resolved by #2193

@lunny lunny closed this as completed Jul 26, 2017
@bard
Copy link

bard commented 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 gogs/gogs#1791 (comment), switched to Gitea because it implemented the feature as noted by @lunny at gogs/gogs#1791 (comment), and am currently using it.

@lunny
Copy link
Member

lunny commented Aug 6, 2017

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

@bard
Copy link

bard commented 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...

@lunny
Copy link
Member

lunny commented Aug 13, 2017

I think we will fix this at some time.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants