On the Mac, a discussion in a git repository carries its own pull requests. You can see their checks, have the room fix what failed, and merge without opening a browser. Pull requests go through GitHub's gh command or GitLab's glab, using the sign-in described on the git page.
The git bar
The strip above the composer shows the repository, the branch and what has changed. Its button offers the next step: Commit, then Push, then Create PR. Once a pull request is open, it offers Fix checks when checks failed or Merge when ready when they pass. The caret beside it holds Stage All, Commit, Push, Compare Branch, Checks, Merge, Create PR, Create Draft PR and Compare On GitHub.
Use Create Draft PR for work you have not read yet, which is most work done while you were away.
The PR rows
Every pull request the discussion opens, or that a seat opens for it, is listed as a row above the git bar. The strip reads like PRs · 2 open · 1 completed, with a needs-you badge when one wants something. Each row has a state and one action that fits it: Fix checks, Resolve conflict, Address review, Mark ready for review, Update branch, Merge #N, or Add to merge queue. Completed rows fold away.
In the transcript, #N for one of the discussion's own pull requests becomes a chip; hover it for a preview card. Turn those off in Settings → Appearance → Display → Pull-request previews.
Fixing checks and comments
How to use it.
- Click Fix checks (or Address review) on the row.
- The room reads the failing log or the review comments, checks the branch out in a worktree of its own, and works there.
- The fix goes back to the same branch, and the row updates when the checks settle.
It does not merge. When not to use it. On a pull request from someone else's fork, where you cannot push.
Merge when checks pass
The row menu's Merge when checks pass… waits for the checks, merges only if they pass, then runs the repository's after-merge steps, such as a deploy or a local install. Set those steps in Settings → Workspace → After a merge. The wait is 180 minutes by default. Branch protection and required approvals still apply.
Looking after it on its own
Each open pull request also has three switches: fix failing checks and comments, merge when ready, and archive the discussion when it is done. They are in the PR pill's menu on the Mac, and under each pull request on the web and the iPhone. The Pull request switches page, linked below, covers them.
Ship check and who wrote what
At Push and Create PR, the app reads the lines being added for keys or tokens, dependencies with known advisories, risky permission changes, duplicated code, and any checks your team or project wrote in words. Findings are shown before the push; they do not block it unless your team made the check a gate. The receipt's Authored row says which seat wrote which lines.
Further reading. Modern Code Review: A Case Study at Google, Sadowski et al., 2018. Pro Git, Chacon and Straub, 2014.