Docs › Pull requests
Merging
Merge a pull request from Origami, by the repository's own rules.
Where Pull requests › Merge
1 min read
How it works
- The band under a request's head says where it stands, such as Ready to merge or Merging is blocked, and what is left in the host's terms: approvals, required checks, open threads or conflicts.
- Its button is the next step: Ready for review for a draft, Update branch when it is behind, Merge when ready where the repository has a merge queue, or Merge.
- The arrow beside Merge picks a method the repository allows, whether the branch is deleted, and the squash commit's message. Where the merge must wait, Enable auto-merge merges it once it can.
- After a merge, Origami can delete your local branch and remove the worktree it made for the request, as Settings › Pull requests says.
Good to know
- Bypass rules and merge is offered only where the host lets you merge as an admin, and asks first.
- GitLab's queue is the merge train, joined with Add to merge train. A request can join a train but not skip it.
- The head's menu has Convert to draft and Close pull request, and Delete branch once it is merged or closed.