Skip to content
GitTree
Hosting integrations

Merge or close a pull request

Merge… asks the provider how the pull request may be merged, shows whether it is Ready to merge, and offers only the Merge methods the repository allows. GitTree merges only while the head is still the commit you looked at; if new commits arrived, nothing is merged.

ProUpdated

Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. Why a merge is blocked
  6. If something goes wrong
  7. Questions
  8. Related

Before you start

  • GitTree Pro or a running trial: pull requests are part of Pro.
  • Permission to merge on the provider, and the pull request reviewed.

Where to find it

  • In the pull request: Merge…, Close… and Reopen…. The palette: Merge Pull Request….
ActionmacOSWindows and Linux
The command palette⌘⇧PCtrl+Shift+P

Steps

  1. Open Merge

    Press Merge…. GitTree asks the provider and shows the state, such as Ready to merge. or Required checks are failing.

  2. Choose the method

    Pick a Merge method: Create a merge commit, Squash and merge, Rebase and merge, Fast-forward only or Semi-linear merge, as the repository allows. Optionally edit the commit title and message.

  3. Merge

    Tick Delete the source branch … afterwards if you want, and press Merge. GitTree says Pull request #… merged.

Expected result

The pull request is merged on the provider. Fetch to see the merge in your graph.

Why a merge is blocked

Merge states the provider reports
GitTree saysWhat to do
The branches conflict.Resolve the conflicts on the branch and push.
Branch protection or required reviews block this merge.Get the approvals the branch needs.
The branch is behind its target and must be updated first.Merge or rebase the target into the branch and push.
A draft cannot be merged.Choose Ready for Review first.

To stop without merging, Close… closes the pull request; Reopen… brings it back.

If something goes wrong

“New commits arrived since you looked. Nothing was merged”

Review the new commits and merge again.

“The provider accepted the merge … and is still carrying it out.”

Press Refresh in a moment to see it merged.

Questions

Does GitTree bypass branch protection?

No. The provider decides every merge; GitTree only asks it, with the method you chose.