Last updated: November 2026
Use this page to create, review, filter, comment on, and merge pull requests (PRs) in GitKraken Desktop on GitHub, GitLab, Bitbucket, and Azure DevOps. On GitHub, you also get GitHub Pull Request View, stacked pull requests, code suggestions, and in-app merge options. To review a pull request, you open it in GitKraken Code Review on GitKraken.dev.
Requirements and limits
- Supported providers on this page: GitHub, GitLab, Bitbucket, and Azure DevOps
- Precondition: Push your branch to the remote before creating a pull request
- GitHub-only features: GitHub Pull Request View, stacked pull requests on GitHub.com, code suggestions, and in-app merge options
- Pull request review: Review on GitKraken.dev opens GitHub, GitLab, and Azure DevOps pull requests in GitKraken Code Review in your browser; it is not available in GitKraken On-Premise (Self-Hosted Server and Serverless)
- Template support: Pull request templates are supported for GitHub, GitLab, and Azure DevOps
- Azure DevOps note: If the PR form does not populate, check the remote URL and integration domain on the Azure DevOps integration page
| Provider | Create PR or MR | View PR or MR | Merge in app | Notes |
|---|---|---|---|---|
| GitHub | Yes | Yes | Yes | GitHub Pull Request View and stacked pull requests are GitHub-only |
| GitLab | Yes | Yes | Yes | Uses merge request terminology |
| Bitbucket | Yes | Yes | Yes | Some reviewer workflows depend on permissions |
| Azure DevOps | Yes | Yes | Yes | Verify remote URL and integration domain if the form does not populate |
Quick Start
To create a pull request: Push your branch to the remote, then use one of these:
- Drag one branch onto another in the graph and select Start a pull request.
- Right-click the target branch and choose the same option.
- Click the + icon in the PULL REQUESTS section of the Left Panel.
To review a pull request: Right-click the pull request in the Left Panel and select Review on GitKraken.dev. The pull request opens in GitKraken Code Review in your browser, where you can review the changes, use AI-generated suggestions, and approve or comment. Review is available for GitHub, GitLab, and Azure DevOps pull requests. For other places to start a review, see How to review pull requests with GitKraken Code Review.
To view a GitHub pull request’s changes in the graph: Right-click the pull request in the Left Panel and select View changes in #N, where #N is the pull request number.
To merge a pull request: Click Merge Pull Request in GitHub Pull Request View and select a merge strategy (merge commit, squash, or rebase).
To create a stacked pull request on GitHub.com: Create a pull request from a branch whose target already has an open pull request. In the Create Pull Request panel, select Start a pull request stack or Add this pull request to an existing stack. GitKraken Desktop shows which pull requests the new one will stack on.
To filter pull requests: Use a predefined filter such as My Pull Requests, or create custom filters in the Left Panel. PR icons show CI status and review state.
How to create a pull request
Push your branch to the remote first. Then use one of these:
- Drag one branch onto another and select Start a pull request
- Right-click the target branch and choose the same option
- Click the icon in the Left Panel PULL REQUESTS section
Use GitKraken Desktop PR creation when: your branch is already pushed and you want to open or manage the PR without leaving the app. Do not start the PR yet when: the branch is not pushed, the target branch is still unclear, or you need provider-specific options not exposed in GitKraken Desktop.
Note: If the Azure DevOps PR form is not populating, see Azure DevOps Integration.
How stacked pull requests work on GitHub.com
A stacked pull request targets the branch of another open pull request. Use a stack to split related work into smaller pull requests while keeping the branch relationship visible.
To create or extend a stack:
- Create a pull request from a branch whose target branch has an open pull request in the same repository. Pull requests from forks cannot be stacked.
- In the Create Pull Request panel, select the stacking option:
- Start a pull request stack appears when the target pull request is not in a stack yet.
- Add this pull request to an existing stack appears when the target pull request is already in a stack.
- Confirm the pull requests listed below the option, such as This pull request will be stacked with #103. Click a pull request number to open it in your browser.
- Click Create Pull Request.
If you change the target branch, GitKraken Desktop clears the stacking option. If GitKraken Desktop creates the pull request but cannot add it to the stack, you see Pull request created, but it could not be stacked.
GitKraken Desktop shows a pull request’s place in its stack in GitHub Pull Request View, the Commit Panel, the graph, and the Left Panel, so you can move between related pull requests.
In GitHub Pull Request View, the header shows the pull request’s position in the stack, such as 2/2. Use the arrows next to it to move between the open pull requests in the stack. Above Merge Pull Request, GitKraken Desktop lists each pull request in the stack down to the base branch, with a status for each one: Ready, Not ready, Draft, Merged, Closed, or Blocked downstack.
When you select a commit that has a stacked pull request, the Commit Panel shows the stack position, such as 1/2, next to the pull request. Hover over the position to see every pull request in the stack, its status, and its branch, down to the base branch of the stack:
- Click an open pull request to open it in GitHub Pull Request View.
- Click a branch to select it in the graph.
- Double-click a branch to check it out.
In the graph, hover over a pull request icon on a branch to see the pull request’s position in its stack. The pull request tooltip in the Left Panel also shows the position.
How pull request templates work
GitKraken Desktop supports PR templates on GitHub, GitLab, and Azure DevOps. After you commit a template to the remote, you can select it in the Template field when you create a pull request.
Tips:
- Store the template where your provider’s documentation says
- Make sure the template is on the branch you have checked out
Resources:
How assignees, labels, and reviewers work
Depending on the integration, you can add these when you create a pull request:
- Assignees
- Reviewers
- Labels
If the source and target branches have a merge conflict, the panel shows Merge conflict detected:
How draft pull requests work on GitHub
With the GitHub integration, select Submit as draft to create the pull request as a draft.
Use a draft pull request when: you want early visibility or feedback before the branch is ready to merge. Do not mark it ready too early when: the implementation still needs major changes and you are not ready for formal review.
How GitHub Pull Request View works
With the GitHub integration connected, open GitHub Pull Request View in either of these ways:
- Select a PR in the Left Panel
- Click the PR icon in Launchpad
Use GitHub Pull Request View when: you want to update PR metadata, check build status, or merge inside GitKraken Desktop. Do not rely on it for every review workflow when: your team depends on deeper provider-native review features outside the app.
From this view, GitHub users can edit:
- Title
- Description
- Reviewers
- Assignees
- Milestones
- Labels
To review the changes, click below the number of changed files. See How to review pull requests with GitKraken Code Review.
How to review pull requests with GitKraken Code Review
Pull requests open for review in GitKraken Code Review on GitKraken.dev, in your browser. Review works for GitHub, GitLab, and Azure DevOps pull requests.
To start a review, use any of these:
- In GitHub Pull Request View, click .
- In the PULL REQUESTS section of the Left Panel, right-click a pull request and select Review on GitKraken.dev.
- In the graph or the Left Panel, right-click a branch that has a pull request and select Review on GitKraken.dev.
- In Launchpad, select Review Pull Request in the pull request’s actions.
GitKraken On-Premise users: Review on GitKraken.dev and Review Pull Request are not available in Self-Hosted Server or Serverless deployments.
In GitKraken Code Review, you can:
- Read the pull request’s diffs
- Get AI-generated review suggestions
- Chat with the rest of your team
- Approve and comment as you would on your hosting service
How to accept or reject suggestions
GitHub Pull Request View lists a pull request’s code suggestions under Code Suggestions:
You can apply or reject each suggestion in the Commit Panel:
How commenting and quoting work
Comment on pull requests, refresh the comments feed, or quote replies:
How branch actions and build status work
In GitHub Pull Request View, double-click a branch to check it out. Click the build status to open the latest build in your browser.
If the branch’s remote is not in your repository yet, GitKraken Desktop prompts you to add it.
How to merge in GitHub PR View
Click to merge.
Choose a merge strategy:
- Create a merge commit
- Squash and merge
- Rebase and merge
If data appears out of sync, refresh GitKraken Desktop.
How the active pull requests panel works
Active PRs appear with this icon 
and are listed in the PULL REQUESTS section of the Left Panel.
Use the predefined filters My Pull Requests or All Pull Requests, or create custom filters.
Tooltips show branch, author, status, and more:
Pull request icons:
- = CI passed and approved
- = CI passed/pending or reviews pending
- = Failing CI or changes requested
How to view a pull request’s changes in the graph
For GitHub and GitHub Enterprise pull requests, you can see all of a pull request’s changes in one diff:
- Right-click the pull request in the PULL REQUESTS section of the Left Panel, or right-click a branch that has a pull request in the graph.
- Select View changes in #N, where #N is the pull request number.
GitKraken Desktop selects the pull request’s base and head commits in the graph, and the Commit Panel shows the full diff of the pull request.
- If the pull request’s branch comes from a remote that is not in your repository, GitKraken Desktop asks whether to add it, for example Do you want to add “fork-owner” as a remote to view “feature-branch”? Accept to add the remote and continue.
- If the base or head commit is not loaded in the graph, a message tells you how old the commit is. Scroll down the graph, or increase Initial Commits in Graph in Preferences > General, then try again.
How merged pull request status appears in the interface
When a pull request is merged, GitKraken Desktop shows a merged PR status pill in 3 places for the branch. The pill appears for GitHub, GitLab, Bitbucket, and Azure DevOps, including GitHub Enterprise, GitLab Self-Managed, and Bitbucket Data Center.
| Location | When it appears |
|---|---|
| Toolbar | When the branch with a merged PR is checked out |
| Commit Panel | When you select a commit on the branch with a merged PR |
| Worktree cards (Agents view) | On the card for the branch with a merged PR |
Use the merged PR pill to confirm that a branch’s work has shipped before you delete the branch or remove its worktree.
