Forks

 

Fork Actions on Change Set Listing Page

All fork actions are available directly from the Source Code page.

Creating Forks / Pull Requests

The following steps are applicable to all registered CodePlex users.

Step 1: Create a new Fork of a Project

image

image

Step 2: Fork Clone, Commit, and Push

image

image

Since this is your repository, you have full capabilities of committing locally, and pushing changes back up to the central server. This is a key distinction for forks, as the changes in your fork ARE NOT pushed into the central project repository.

Central project changeset history:

image

Fork changeset history:

image

Gitk:

image

 

Step 3: Create a Pull Request

Once you have pushed all of your changes to your fork (as well as making sure you have pulled the latest changes from the central repository), you’re ready to create a pull request.

image

image

 

Applying Pull Requests

The following steps are applicable to project coordinators or developers for a project only.

If you are a Mercurial project owner, and need to get access to unapplied patches, please contact us.

Step 1: Reviewing / Apply Pull Request

image

image

image

image

 

Step 2: Incorporating the pull request

After you’ve reviewed the changes, you may decide to merge the pull request into your project source. Clicking the Accept link in the pull request view page will bring up a dialog with detailed instructions on how to merge the code:

image

Note that merely accepting the pull request does not automatically merge the changes into your code. You’ll need to follow the manual steps provided in this dialog box to complete the task.

If you decide not to accept the pull request, you can use the Decline link. Keep in mind that it’s courteous to give really good feedback when declining a pull request. The user is now able to send another pull request with new changes they’ve made to their fork.