Ready to land
Pull requests GitHub will merge now, or once the branch is updated, with the buttons to land them.
On this page
Ready to land lists open pull requests that GitHub says can merge now (Ready to merge) and those that only need their branch brought up to date first (Behind trunk). Where you can push to the repository, each card has the buttons to land it. An approved pull request scores higher than one nobody has approved yet.
#What you see
- Ready to merge: GitHub will merge it now. This includes a pull request whose only red checks are ones the branch does not require, because GitHub's own merge button merges it too.
- Behind trunk: the repository requires branches to be up to date, and this one is not. GitHub will not merge it until the branch is updated.
A pull request stacked on another open pull request is not listed as ready to merge: it lands after its parent. Your own ready pull requests are in My turn under Your PRs, with the same buttons. Dependency updates are in Dependencies.
#What you can do
Merge
Merge opens the merge options: Create a merge commit, Squash and merge or Rebase and merge, as the repository allows. Limn reads the live merge state from GitHub only when you press the button, and checks it again before it merges. With a row selected, m merges it.
Merge when ready
Merge when ready arms Limn's own auto-merge for this pull request: Limn merges it as soon as it can land, while the app is running. If new commits are pushed after you arm it, Limn does not merge them without you. Cancel auto-merge stops it. See Merge when ready.
Update branch
Update branch brings the base branch's new commits into the pull request's branch on GitHub. The card then waits for the checks to run again.
Merge queues
In a repository that uses GitHub's merge queue, the buttons read Add to merge queue and Queue when ready. A queued pull request shows In the merge queue with what the queue is doing, and Remove from queue; Merge and Merge when ready are hidden, because GitHub merges it from there. See Merge queues.
#Why it helps
Finished work that sits unmerged goes stale and starts to conflict. This tab shows it in one place and lets you land it without opening each pull request. See also Can it land?