将 github 上的 git repo 复制/分叉到同一组织中

Question

I have a repo on github that contains a web application that's deployed to two different domains. The application has slight logic forks here and there to behave differently depending on which domain it's deployed to.

It's come to the point to where I want to split it into two separate repos, one for each domain.

Github won't let me fork it into the same organization. Searching for "git duplicate repo" suggests I should bare clone and mirror push it, but that seems to be for keeping both repos in sync, which I don't want to do.

What's the best way to go about this? I'd like to preserve the old commit history in the new copy if possible.

Answer 1

Just create a new repository and push to it from your working copy:

git clone git@github.com:me/myrepo-original
cd myrepo-original
git remote set-url origin git@github.com:me/myrepo-new
git push origin master

Now you have a new repository, myrepo-new , which is identical to myrepo-original .

Answer 2

If you do not need the fork relation (eg you want some kind of decoupled alternate repo for whatever reason), duplicating the repo as outlines by your Google finds and larsks's answer is fine.

If you do want to make it a fork, contact Github support (support@github.com or https://github.com/support ), and they will create a fork in the same organization for you. (They're not picky about this either, you'll have just to provide an alternative name for the repo, as repo names within an account must be unique.)

---

Update : User Steve Rice reports in the comments below that GitHub Support stated that support would not currently/no longer set up a second fork in your account.

GitHub recently posted an article about possible alternatives to forking a repo into the same account. You can read that article here .

Answer 3

Use Github's Import Repository option on the + menu on top of the page or just open

https://github.com/new/import

This creates a new repository with the exact contents of the copied repository. The downside (the same as for git commands answer by Iarsks ) is that it doesn't count as a fork for Github.

Answer 4

Another way would be to add the original repo, to be copied, as remote for our current repo.

#create a new repo in the org1 organization called myrepo-new

In your local terminal, run:

git clone git@github.com:org1/myrepo-new
cd myrepo-new
git remote -v #shows current repo link on github as origin
git remote add name-for-remote https://github.com/org1/repo-old
git remote -v #shows repo-old as name-for-remote
git fetch  name-for-remote
git merge name-for-remote/branch-to-get-from-remote
#Now fix any conflicts if present
#If number of files/commits is very high, the desktop client may hang when you try to commit your changes after merge. Try switching to Git Shell if this happens.
git status 
git commit -m "commit message"
git push origin master

Answer 5

I know this is a super old thread, but I stumbled across it looking for the the answer and subsequently found a better way:

Make the repo you want to copy a template repo. It is a check box at the top of the repository settings. After you do this, there will be a big green button labeled "Use this template" at the top of the repo next to the Code button. Click that, and it will make a copy of the repo in whichever account you want.

Answer 6

Alternative solution:

Create a new organisation and fork it there. If the repo is private, it will stay private in the new org as well. Then you can give access to external devs or whoever you want to the forked repo and they can raise PRs back to original repo.

Answer 7

You can mark the first repo as a Template (in settings) and then "Use" that template repo when you create a new repo. It's not exactly a fork, but functionally equivalent in some respects.

Answer 8

Github won't let me fork it into the same organization

GitHub does let you fork within the same organisation, since June 2022.

Improved innersource collaboration and enterprise fork policies

Previously, three aspects of repository forks caused friction to innersource collaboration and administration:

1. Repositories could not be forked within a single organization.
2. Repositories with internal visibility could not be forked to an organization.
3. Enterprise owners lacked control over where repositories could be forked.

These obstacles have been addressed with the following new features. We're always looking for new ways to improve repository collaboration and we welcome your ideas .

Fork a repository to the same organization as its parent

Previously, a repository could be forked only to a different organization or user account.

Now, a repository can be forked to the same organization as its parent repository , addressing situations where people are working in one organization and don't want to fork a repository to a different organization or user account.

Answer 9

Couldn't you just duplicate the local folder, delete the git stuff:

rm -rf .git*

Then make a new repository in that folder? Seems cleaner and easier.