Simply add the new remote (Organization) to your old repository (master). Once you did it simply push the branch A to the new (organization) repository. Now you should have the new branch A in your new repository. The point is to add new remote and to push the branch to your new repository.
I started with @user292677's idea, and refined it to solve my problem:
$ git push https://github.com/accountname/new-repo.git +new-project:master
The new Github repo is finished. The result is;
master
corresponds to the old repo's new-project, withIn fact, I found that by using this method, I could create the new repo with a hand-picked selection of branches, renamed as I wanted:
$ git push [email protected]:accountname/new_repo +new-project:master +site3a:rails3
The result is that the pre-existing site3a branch is now also moved to the new repo and will appear as rails3. This works really well: the network diagram shows the new master and rails3 with full history and in their correct relationship to each other.
Update 2013-12-07: Used this with another project, and verified that this recipe still works.
Update 2018-01-11: Updated step 3. to use GitHub recommendation for https protocol. Recipe still works.
Update:
cd to local repo containing old_branch and:
$ git push https://github.com/accountname/new_repo.git +old_branch:master
And that is all. (Note: git history preserved)
I had tried the answer above and found it not specific enough as it didn't specify +master:master which is what I needed to make it work. It works great.
Source (with my modifications to avoid ssh issues with github): Mauricio Aiello, former Java Senior Developer, https://www.quora.com/How-do-I-create-a-new-GitHub-repository-from-a-branch-in-an-existing-repository
git clone -b new-project /path/to/repo /new/repo/path
Edit: Within GitHub, you can “fork” the repo, then go to the Admin tab in your clone. Beneath “Repository name” and “Visibility” is “Default Branch” with a drop-down menu of branches. Choose new-project
.
Re-edit: I just realized it’s the master
branch you want set, not just the “default” branch. So…
them/repo
to you/repo
. git clone [email protected]:you/repo.git
gitk
. old-master
branch so you don’t lose track of the old commits.] new-project
branch, right-click on the commit message, and select “Reset master branch to here”. (You can also do this at the command line using git-reset
, but I haven’t figured out the correct invocation.)Your next push up to your GitHub repo will need to be done with the --force
option, but otherwise you’re done.
If it’s one of your own repos you’re doing this to…
git clone [email protected]:you/orig.git
git clone orig copy
copy
repo, reset the master
branch to where you want it. you/copy
. Follow the directions on GitHub to set up that project as a remote for your local version of copy
, push master
, and you’re done!Not sure whether this is a good way, but it's easy anyway:
git clone -b new-project [email protected]:User/YourProject.git newProjcet
Then create a new repo on github, and push it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With