Skip to main content

​
Overview

Pull requests (PRs) are the primary way to propose, review, and merge changes in collaborative Git workflows. GitHub Desktop provides seamless integration with GitHub pull requests.

Create PRs

Create pull requests directly from the app

Review Changes

View PR status, checks, and reviews

Checkout PRs

Check out pull requests for local testing

Branch Management

Automatically manage fork remotes for PR branches

​
Creating Pull Requests

​
Create from Branch

1

Push Your Branch

Ensure your branch is published to the remote:
  • Click Publish branch if it’s not yet published
  • Or Push origin if you have new commits
2

Open PR Creation

Click Branch > Create Pull Request or press Ctrl+R (Windows/Linux) or Cmd+R (macOS)
3

Configure on GitHub

GitHub Desktop opens your browser to GitHub’s PR creation page with:
  • Base branch pre-selected
  • Your branch as the compare branch
  • Commit messages pre-filled
4

Complete on GitHub

On GitHub:
  • Review the title and description
  • Add reviewers and labels
  • Assign to project boards
  • Click Create pull request

​
Create from Fork

When working on a fork:
1

Ensure Upstream is Set

GitHub Desktop automatically detects the parent repository
2

Push to Fork

Publish or push your branch to your fork
3

Create Pull Request

Click Branch > Create Pull Request
4

Select Base Repository

On GitHub, ensure the base repository is the upstream (not your fork)

​
Viewing Pull Request Status

​
PR Information in GitHub Desktop

When on a branch with an associated pull request: Branch Badge
  • PR number and title appear in the branch dropdown
  • Visual indicator shows PR state (open, merged, closed)
Pull Request Tab
  • Click to view PR details
  • See review status
  • Check CI/CD status
  • View merge conflicts
Checks and Reviews
  • CI/CD check results
  • Required reviews status
  • Merge conflicts detection
  • Branch protection rules

​
Pull Request States

The pull request is open and under review:
  • Green icon
  • Can push new commits
  • Can request reviews
  • Can merge when ready
The pull request has been merged:
  • Purple merged icon
  • Branch can be safely deleted
  • Commits are now in the base branch
The pull request was closed without merging:
  • Red closed icon
  • Changes were not merged
  • Can be reopened if needed
The pull request is marked as a work in progress:
  • Gray draft icon
  • Cannot be merged until marked ready
  • Useful for early feedback

​
Checking Out Pull Requests

​
Check Out Your Own PR

1

View Pull Requests

Click Branch > Pull Requests
2

Select PR

Choose the pull request from the list
3

Checkout

Click Check out to switch to the PR branch

​
Check Out Someone Else’s PR

For pull requests from forks:
1

Open PR List

Click Branch > Pull Requests
2

Find PR

Search or browse for the pull request
3

Checkout from Fork

Click Check out
  • GitHub Desktop automatically adds a remote for the fork
  • Downloads the branch
  • Switches to the PR branch
GitHub Desktop automatically manages fork remotes using the prefix github-desktop- to keep your remote list clean.

​
Fork Remote Management

From the technical documentation: 
// GitHub Desktop uses a magic prefix for fork remotes
export const ForkedRemotePrefix = 'github-desktop-'

// Remotes are cleaned up when PRs are closed
function forkedRemotesToDelete(
  remotes: ReadonlyArray<IRemote>,
  openPullRequests: ReadonlyArray<PullRequest>
): ReadonlyArray<IRemote> {
  const forkedRemotes = remotes.filter(remote =>
    remote.name.startsWith(ForkedRemotePrefix)
  )
  
  const remotesOfPullRequests = new Set<string>()
  openPullRequests.forEach(openPullRequest => {
    const { gitHubRepository } = openPullRequest.head
    if (gitHubRepository?.cloneURL) {
      remotesOfPullRequests.add(gitHubRepository.cloneURL)
    }
  })
  
  // Delete remotes for closed PRs
  return forkedRemotes.filter(
    forkedRemote => !remotesOfPullRequests.has(forkedRemote.url)
  )
}
Key Features:
  • Automatic remote creation for fork PRs
  • Cleanup when PRs are closed
  • Prevents remote list from growing unbounded
  • Uses github-desktop- prefix for namespace safety
Do not manually create remotes starting with github-desktop- as they may be automatically deleted by GitHub Desktop.

​
Updating Pull Requests

​
Adding Commits

Add more commits to an open pull request:
1

Ensure You're on PR Branch

Check out the pull request branch
2

Make Changes

Edit files and commit as usual
3

Push Changes

Click Push origin to update the pull request
4

Verify on GitHub

The new commits appear automatically in the pull request

​
Responding to Review Comments

1

View Reviews

Open the pull request on GitHub to see review comments
2

Make Requested Changes

In GitHub Desktop, make the changes requested by reviewers
3

Commit and Push

Commit your changes with a descriptive message referencing the review
4

Resolve Conversations

On GitHub, mark conversations as resolved

​
CI/CD Integration

GitHub Desktop shows the status of GitHub Actions and other CI checks:

​
Check Status Indicators

  • Pending: Yellow circle - checks are running
  • Success: Green checkmark - all checks passed
  • Failure: Red X - one or more checks failed
  • Required: Checks that must pass before merging

​
Viewing Check Details

1

Click PR Tab

Select the pull request in GitHub Desktop
2

View Checks

See all checks and their status
3

Open Details

Click View on GitHub to see full check logs

​
Merge Conflicts in PRs

When your pull request has conflicts with the base branch:
1

Conflict Notification

GitHub Desktop shows a merge conflict indicator
2

Update from Base Branch

  • Click Branch > Update from [base-branch]
  • Or merge the base branch into your PR branch
3

Resolve Conflicts

Use GitHub Desktop’s conflict resolution tools
4

Push Resolution

Commit and push the conflict resolution
5

Merge on GitHub

Once conflicts are resolved, merge the PR on GitHub

​
Suggested Next Actions

After creating a pull request, GitHub Desktop suggests next actions:
  • View on GitHub: Open the PR in your browser
  • Create another PR: Create another pull request from a different branch
  • Switch branches: Continue working on another branch

​
Branch Protection and PR Requirements

GitHub Desktop respects branch protection rules:

​
Protected Branch Indicators

  • Required reviews: Shows how many reviews are needed
  • Required status checks: Lists checks that must pass
  • Restricted push: Indicates if force push is blocked
  • Admin enforcement: Shows if admins must follow rules

​
Pull Request Reviews

  • Approved: Green checkmark - reviewers approved changes
  • Changes requested: Red X - reviewers requested changes
  • Commented: Gray - reviewers left comments without approval
  • Pending: Yellow - waiting for reviews

​
Draft Pull Requests

Create draft pull requests for early feedback:
1

Create PR on GitHub

After clicking Create Pull Request in GitHub Desktop
2

Mark as Draft

On GitHub, click the dropdown next to Create pull request and select Create draft pull request
3

Work in Progress

Continue making commits to the draft PR
4

Ready for Review

Click Ready for review on GitHub when complete

​
Pull Request Templates

If your repository has PR templates:
  1. Templates are automatically loaded when creating PRs on GitHub
  2. Fill in the template sections
  3. Templates help ensure consistent PR descriptions
  4. Common sections: Changes, Testing, Screenshots, Related Issues

​
Comparing Branches Before Creating PRs

Preview changes before creating a pull request:
1

Compare to Branch

Click Branch > Compare to Branch
2

Select Base Branch

Choose the branch you plan to merge into
3

Review Differences

See:
  • Commits that will be included
  • Files that changed
  • Line-by-line diffs
4

Create PR

If satisfied, create the pull request

​
Best Practices

Keep PRs focused: Smaller, focused pull requests are easier to review and merge faster than large, complex ones.
  1. One Feature per PR: Each pull request should address a single feature or bug fix
  2. Write Clear Descriptions: Explain what changed and why
  3. Link to Issues: Reference related issues with Fixes #123 or Relates to #456
  4. Request Appropriate Reviewers: Tag reviewers who are familiar with the code
  5. Respond to Feedback: Address review comments promptly
  6. Keep PRs Updated: Regularly update from the base branch to avoid conflicts
  7. Test Before Creating: Ensure your changes work before opening a PR
  8. Use Draft PRs: Mark work-in-progress PRs as drafts

​
Keyboard Shortcuts

ActionWindows/LinuxmacOS
Create pull requestCtrl+RCmd+R
View on GitHubCtrl+Shift+GCmd+Shift+G

​
Troubleshooting

If you can’t create a PR:
  • Branch not pushed: Publish your branch first
  • No changes: Ensure you have commits that differ from the base branch
  • Not signed in: Sign in to your GitHub account in GitHub Desktop
  • No write access: Verify you have permission to create PRs
If a pull request doesn’t appear:
  • Refresh the repository (Repository > Fetch origin)
  • Ensure you’re signed in to the correct GitHub account
  • Check that the PR is for this repository (not a different fork)
  • Verify the PR hasn’t been closed or merged
If checking out a fork PR fails:
  • Check your internet connection
  • Verify you have read access to the fork
  • Try fetching manually: Repository > Fetch origin
  • Check for network/proxy issues
If CI/CD checks don’t update:
  • Click Repository > Fetch origin to refresh
  • Verify GitHub Actions are enabled on the repository
  • Check if the workflow is configured correctly
  • View the PR on GitHub for real-time status

Build docs developers (and LLMs) love

Get started for freeTalk to us