Pull Requests

A pull request (sometimes called merge requests), is a review request. You are asking someone to check the changes on a branch before merging into another branch.

Creating a pull request

If connected to a remote on GitHub, GitLab, Bitbucket, or Visual Studio Team Services, create pull requests by dragging and dropping one branch to another and selecting Start a pull request.

Alternatively, try right-clicking the target branch and selecting Start a pull request.

Or click the in the pull requests section on the left panel, and select the repo and branch to create the pull request.

Pull request templates

GitKraken supports pull request templates from your GitHub, GitLab, and Azure DevOps (including legacy VSTS URLs).

Once your pull request templates are commited to your remote, the template field will appear when you create a pull request in GitKraken:

If this is your first time working with pull request templates, consider reviewing the following instructions for GitHub, GitLab, or Azure DevOps pull request templates.

Assignee, Labels, and Reviewers

Some integrations will allow you to also add a pull request assignee and label(s) to your pull request. GitKraken will then pass these values onto your remote service when the pull request is created.

Note - When creating pull request, GitKraken will now detect whether your source branch has conflicts with the target branch in the pull request modal.

Depending on the integration, you may also add reviewers and multiple assignees to a pull request.

Note: Because pull requests occur in the remote, first push your branch before creating the request.

Working with active pull requests

GitKraken displays active pull requests in your graph with this icon.

If using the integration with GitHub, GitLab, Azure DevOps, or Bitbucket, you may hover over the pull request in the left panel to get a quick view of when the pull request was opened and for which branches.

For the GitLab integration, this tooltip will also show any assignee or labels associated with the pull request.

And for GitHub, this tooltip will show assignees, labels, reviewers, and build status.

If the branch changes look good after review, you or a reviewer may merge the branch.

However if there are outstanding questions or comments, users can leave a comment on the pull request.

If other changes are required, make the change to your code, and then commit and push to your existing branch. Updating your branch updates the pull request too.

Read more about using pull requests on our blog.