Create a private fork of a public repository

private_fork.md

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

1. Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

   git clone --bare [email protected]:usi-systems/easytrace.git

2. Create a new private repository on Github and name it easytrace.

   If you are unable to create a private repo, you can request unlimited private repos as a studant by getting the student pack from Github.

3. Mirror-push your bare clone to your new easytrace repository.

   Replace <your_username> with your actual Github username in the url below.

   cd easytrace.git
   git push --mirror [email protected]:<your_username>/easytrace.git

4. Remove the temporary local repository you created in step 1.

   cd ..
   rm -rf easytrace.git

5. You can now clone your easytrace repository on your machine (in my case in the code folder).

   cd ~/code
   git clone [email protected]:<your_username>/easytrace.git

6. If you want, add the original repo as remote to fetch (potential) future changes. Make sure you also disable push on the remote (as you are not allowed to push to it anyway).

   git remote add upstream [email protected]:usi-systems/easytrace.git
   git remote set-url --push upstream DISABLE

   You can list all your remotes with git remote -v. You should see:

   origin	[email protected]:<your_username>/easytrace.git (fetch)
   origin	[email protected]:<your_username>/easytrace.git (push)
   upstream	[email protected]:usi-systems/easytrace.git (fetch)
   upstream	DISABLE (push)
   

   When you push, do so on origin with git push origin.

   When you want to pull changes from upstream you can just fetch the remote and rebase on top of your work.

     git fetch upstream
     git rebase upstream/master

   And solve the conflicts if any

7. Make your easytrace repo available in your Vagrant VM by adding the following to your Vagrantfile

   Replace "~/code/easytrace" with your local path to the easytrace repo.

   config.vm.synced_folder "~/code/easytrace", "/easytrace"
   

8. Reload your VM to enable the synced folder (in the folder containing your Vagrant file).

   vagrant reload 

9. The easytrace repo is available at /easytrace once you ssh into the machine.