A pull opens on its verdict

This page is for anyone who reviews or merges a pull. Every pull opens on one line: can it land, and if not, what holds it.

Where you see it

What it says

One of: Ready to land, Waiting for a review, A reviewer asked for changes, Waiting for a team's review, Waiting for the check, The check failed, Conflicts with <base>, Merges on the origin, Merged, Closed without merging. The words are asked in the order the merge box and the merge itself ask them, so the line never says Ready where the merge would refuse.

Beside it, one action when you can take it: Go to merge (scrolls to the merge box on Files), Review, See the check, or Resolve for a conflict. It is a link; the merge itself is still the button in the merge box.

Which base the green was checked on

A pull's check runs on the merge of its head with the base, so a green is only as fresh as that base. When the base moves after the check, the verdict says Checked against an older <base>, the merge waits for a re-check, and every door names the base tip the green was tested on:

To see how far behind a green is, compare checkedAgainst with the base branch's tip; Check again (or C in the terminal) asks for a fresh one.

Try it

Open any pull at /<owner>/<repo>/pulls/<number>; its first line is the verdict. Over ssh, open the pull from the repository's list.

When a pull's check failed while its base branch is red, one more sentence names the base's failing tests, and ends "red on main, not on this pull" if the pull fails only those. The page and the terminal screen say it; a pull whose check has not failed hears nothing.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs