10000 Allow to fork repository into the same owner by wxiaoguang · Pull Request #32819 · go-gitea/gitea · GitHub
[go: up one dir, main page]
Skip to content

Allow to fork repository into the same owner #32819

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Dec 14, 2024
Merged

Allow to fork repository into the same owner #32819

merged 2 commits into from
Dec 14, 2024

Conversation

wxiaoguang
Copy link
Contributor
@wxiaoguang wxiaoguang commented Dec 13, 2024 •
edited
Loading

This feature is experimental, not fully tested, and may be changed in the future.

It is only designed for users who really need it: set [repository].ALLOW_FORK_INTO_SAME_OWNER=true in your app.ini

Doc: https://gitea.com/gitea/docs/pulls/122

image

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Dec 13, 2024
@github-actions github-actions bot added modifies/go Pull requests that update Go code docs-update-needed The document needs to be updated synchronously labels Dec 13, 2024
@wxiaoguang wxiaoguang mentioned this pull request Dec 13, 2024
Closed
@wxiaoguang wxiaoguang added this to the 1.23.0 milestone Dec 13, 2024
@wxiaoguang wxiaoguang added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Dec 13, 2024
@wolfogre
Copy link
Member

Wow, I believe I need this. I used to do this by forking the repo to a new owner and transferring it back with a different name.

@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Dec 13, 2024
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Dec 14, 2024
@wxiaoguang wxiaoguang merged commit a66c16d into go-gitea:main Dec 14, 2024
26 checks passed
@wxiaoguang wxiaoguang deleted the fix-fork-owner branch December 14, 2024 01:40
@wxiaoguang wxiaoguang mentioned this pull request Dec 18, 2024
Merged
@AsgeirSH AsgeirSH mentioned this pull request Jan 17, 2025
Open
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Mar 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@wolfogre wolfogre wolfogre approved these changes

@Zettat123 Zettat123 Zettat123 approved these changes

Assignees
No one assigned
Labels
docs-update-needed The document needs to be updated synchronously lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/go Pull requests that update Go code type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Milestone
1.23.0
Development

Successfully merging this pull request may close these issues.
4 participants
@wxiaoguang @wolfogre @Zettat123 @GiteaBot
0