DP Code Migration to GitHub

From DPWiki
Jump to navigation Jump to search

In March 2018, the DP development team moved code hosting providers from Sourceforge to github.com. This page provides instructions on how to assist developers with that migration.

Updating your git repo

The following walks you through instructions on forking the new repo on github.com and updating your existing local git repo to point to it instead.

  1. If you don't have a github.com account already, create one at https://github.com
  2. After you have an account, access the dproofreaders project at https://github.com/DistributedProofreaders/dproofreaders
  3. Fork the repository by clicking Fork in the upper right
    • Click on your github username as the location to create the fork. Note that at the bottom of the popup there will be a message that seems to say you don't have authority to create a fork. But what it really says is that you can't create your fork in *dproofreaders*.
  4. After a few seconds, this will take you to your forked copy of the dproofreaders repo under your username (eg: https://github.com/cpeel/dproofreaders)
  5. You'll need to set up SSH keys for github.com, just like you did for Sourceforge, to fetch and push code. You can do so at https://github.com/settings/keys

On your development system (eg: the Test server)

# Go to your git checkout and list your remotes:
git remote -v
# Update the origin and upstream remotes to point to github.com
# Below, <github_username> is your github.com username
git remote set-url origin git@github.com:<github_username>/dproofreaders.git
git remote set-url upstream https://github.com/DistributedProofreaders/dproofreaders.git

Now you can push up your repo to your new GitHub repository:

git push origin master
# repeat for any other branches besides master that you want to push up.

See DP Code Development Using git#Refreshing your fork for details on how to refresh your local repo with the latest code from github.com.