github desktop transfer commits from fork

#Github desktop transfer commits from fork update#
#Github desktop transfer commits from fork code#
#Github desktop transfer commits from fork series#

I apologize for any incorrect terminology, I'm still fairly new to using git and Github, so still trying to figure out all of its possibilities.

Continue business as usual now owning the original repo which contains a branch that used to be my fork.

current owner transfer's ownership (and therefor also the branch containing my modified code) to me on Github.

Delete the fork from my account on Github.

create new branch on repo1 using the hash of the fork, effectively cloning the fork into repo1.

#Github desktop transfer commits from fork code#

The fork I have is mostly new code that will slowly be worked into the original repo, so I want to keep it up to date with original repo and don't want to break it off as its own separate repo.įrom playing around with some empty test repos and forks, is this the proper way to transfer the original repo to me without losing or merging my personal changes within my fork: Problem is that apparently Github doesn't like to transfer ownerships when someone has has a fork of that repo on their account.

After helping out the original repo's dev with some code, he's ready to retire from it himself and wants to transfer ownership of it to me. On GitHub, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created. The original post can be found here.I have forked a repo on Github and made my own modified version of the code. This article has been provided by Alan Coggins and was originally published on Simpl圜. Now you are ready to start working in GitHub Desktop.

Then delete the branch that was originally created.

Check that you have the new default branch with your unique name.

On the main screen, click the Branches section in the top menu to see all the current branches. You will get a warning message – click the button to continue. After you fork a repository, you can fetch updates from the upstream repository to keep your fork up to date, and you can propose changes from your fork to the upstream repository with pull requests.

#Github desktop transfer commits from fork update#

Enter the name of a new branch – just use a minor variation of the current default branch.Ĭlick the Update button to set this as the default branch. Forks let you make changes to a project without affecting the original repository, also known as the 'upstream' repository.Click on the Branch button to get the dropdown box of current branches.You will need to follow the procedure outlined below.

The default branch is often called master, but in our case it is develop. The solution is to create a new branch with another name in your fork, make it the default and then delete the branch that was created originally. GitHub Desktop needs these two to have different names. Creating a fork automatically makes a default branch in your fork with the same name as the default branch in the upstream repo. GitHub Desktop has a quirky limitation that has been discussed numerous times online but remains unfixed. That’s it! It will now complete the process for you.

Then click the “Fork” icon in the top right.

Make sure it still shows you as logged in to your account.

A message will briefly appear letting you know that the. In the top-right corner of the window, youll see a 'Fork' button with a number to the right of it, which represents the number of times the repository has been forked.

For this example we will be forking Classic Commerce, so we go to the main Classic Commerce repo. To fork a repo, log in to your account and then go to the repository you want to fork. Once that is set up and you are logged into your account, find the repo on GitHub that you want to fork. You will need your own GitHub account before you can begin. Use fork and clone to get a copy of someone elses repo if theres any chance you will want to propose a change to the owner, i.e. To clone the repository using HTTPS, under 'HTTPS', click. Click the copy to clipboard button to copy the. We will be using the HTTPS address to clone. On GitHub, navigate to your fork of the Spoon-Knife repository. First, we will click the green Code button that will drop options to clone the repository. This is called a fork and it involves copying the files from the “official” repo (upstream) to your own account (origin). You can clone your fork with the command line, GitHub CLI, or GitHub Desktop. You obviously can’t work directly on the main project files, so you first need to take a copy of them to your own GitHub account. For the introductory piece you can visit here.

#Github desktop transfer commits from fork series#

This article is part of a series on Github Desktop.