GitHub Monitor 2.3.1

• What was said about a pull request is now shown, not just counted.
  The pane read the conversation tab's total and stopped there, so a
  remark nobody had hung on a line of the diff -- a question about the
  approach, an objection, the sentence that decides whether the thing
  gets merged -- could only be read in a browser. It now reads the same
  way the issue pane always has: the newest few under the description,
  with "N older on GitHub" when there are more.

• A remark that will not fit on one line takes two. Somebody else's
  comment was sometimes cut off at the right of the column with an
  ellipsis. The thread was never too narrow — a paragraph was told how
  wide it might be and nothing about growing downwards, so one holding
  something unbreakable, a URL or a long path or a code span, was given
  a single line's height and had to truncate. Ordinary prose wrapped,
  which is why it only happened sometimes.

• Settling a conversation folds it there and then. Whether it
  arrived folded was decided once, when the diff was built, so a
  conversation resolved while you were looking at it stayed open until
  the next time. Unsettling opens it again, and the chevron still
  overrules both — a conversation you opened by hand stays open.

• The folded line is blue, not grey. Drawn in the secondary label
  grey it sat among grey source-code comments and disappeared into
  them. It is a cyan now, far enough from the blue that marks an
  unsettled conversation that the two do not read as one mark, and dark
  enough to clear 4.5:1 on every ground the diff draws on.

• The list of names is not painted over any more. Typing @ in a
  remark showed a list with the diff's coloured lines running through
  it, which read as transparency and was not: the list hangs out of the
  box it belongs to, and the rows below that box are painted after
  it, straight over the part that had escaped. Leaving your own bounds
  does not change where you sit in the painting order. The row holding
  an open box is lifted above its neighbours now, and so is a
  conversation being replied to, which holds the same box.

• A comment in the code stays a comment. The prose inside a
  docblock was syntax-highlighted as code, so any word that happens to
  be a keyword — and, for, return — came out purple in the middle
  of a sentence. The diff hands the highlighter one line at a time, and
  every line after the opening /** arrived with no memory of being
  inside anything; it carries that now. A // inside a string still
  opens nothing, and a PHP attribute is still an attribute.

• A diff with a conversation on it scrolls like one without. The
  arithmetic that works out which line each conversation hangs off was
  redone from the raw patch every time the view was drawn — and the
  view is drawn again whenever the pointer crosses a row. It is the one
  piece of a patch's reckoning that runs only when somebody has
  commented, which is exactly why a commented file scrolled worse than
  the same file without one. On a nine-hundred-line patch that was
  three quarters of a millisecond a go; it comes from the cache now, at
  a fiftieth of the cost, and the line numbers beside it with it.

• The diff's header fits on one line. It led with 6 files changed
  in bold, which at any ordinary window width wrapped onto two lines
  and pushed the rest along. The number is already in the tick count
  beside it, in the pager, and in the tree down the side; the pager now
  carries the weight instead, and nothing in the bar may wrap.

• Escape closes the box, and nothing further out. Unhandled, it
  travelled on to the diff, which took it for "put this away" and shut
  the whole overlay — with the half-written remark in it. It now means
  the innermost thing on screen: the list of names where one is up, the
  box once it is gone, the diff only when neither is.

• The list of names is opaque. The window's own background colour
  is not, so the code behind it showed through the logins — unreadable
  in exactly the place it had to be read.

• The caret is in the box when it opens. It is opened by somebody
  who means to write in it — the plus in the gutter, or Reply on a
  conversation — so asking for a click into it first was a click for
  nothing. In a box that already holds something, a reply being
  reworded or a remark being edited, the caret goes to the end of it.

Install

brew tap sidler/tap
brew trust --cask sidler/tap/githubmonitor
brew install --cask githubmonitor

Already have it? brew upgrade --cask githubmonitor.

Or download the zip below, unpack it and move GitHubMonitor.app to
/Applications.

Signed with a Developer ID and notarised by Apple, with the ticket stapled
to the bundle.