Article version: Enterprise Server 2.13

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-03-27. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Committing changes to a pull request branch created from a fork

You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator.

You can only make commits on pull request branches that:

Only the user who created the pull request can give you permission to push commits to their branch. For more information, see "Allowing changes to a pull request branch created from a fork."

Note: You can also make commits to a pull request branch from a fork of your repository through your GitHub Enterprise Server instance by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "Creating a pull request from a fork."

  1. On GitHub Enterprise, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created.

  2. Under the fork's repository name, click Clone or download.

    Clone or download button

  3. In the Clone with HTTPs section, click to copy the clone URL for the repository.

    Clone URL button

  4. Open TerminalTerminalGit Bashthe terminal.

    Tip: If you prefer to clone the fork using GitHub Desktop, then see "Cloning a repository to GitHub Desktop."

  5. Change the current working directory to the location where you want to download the cloned directory.

    $ cd open-source-projects
  6. Type git clone, and then paste the URL you copied in Step 3.

    $ git clone https://hostname/USERNAME/FORK-OF-THE-REPOSITORY
  7. Press Enter. Your local clone will be created.

    $ git clone https://hostname/USERNAME/FORK-OF-THE-REPOSITORY
    > Cloning into `FORK-OF-THE-REPOSITORY`...
    > remote: Counting objects: 10, done.
    > remote: Compressing objects: 100% (8/8), done.
    > remove: Total 10 (delta 1), reused 10 (delta 1)
    > Unpacking objects: 100% (10/10), done.

    Tip: The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory.

  8. Navigate into your new cloned repository.

  9. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.

    compare-branch-example In this example, the compare branch is test-branch:

    $ git checkout test-branch

    Tip: For more information about pull request branches, including examples, see "Creating a Pull Request."

  10. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into it, including master. Make modifications as you like.

  11. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is test-branch:

    $ git push origin test-branch
    > Counting objects: 32, done.
    > Delta compression using up to 8 threads.
    > Compressing objects: 100% (26/26), done.
    > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
    > Total 29 (delta 8), reused 0 (delta 0)
    > To https://hostname/USERNAME/FORK-OF-THE-REPOSITORY.git
    > 12da2e9..250e946  test-branch -> test-branch

Your new commits will be reflected on the original pull request on your GitHub Enterprise Server instance.

Further Reading

Ask a human

Can't find what you're looking for?

Contact us