What the thread states mean

Resolved, Likely addressed, Replied and Untouched: how Limn reads each review thread, and why Likely addressed is a guess.

On this page

Limn gives every review thread on a pull request one of four states, from what GitHub reports and from the commits that came after the thread. The states show on the Threads tab, in the Feed, in the sidebar's thread bars and in the Timeline's filters. They answer one question: does this comment still need someone?

#The four states

StateWhat it means
ResolvedMarked resolved on GitHub.
Likely addressedA commit touched the thread's file after the last comment. This is a guess.
RepliedSomeone replied, but the thread is not resolved and no later commit touched the file.
UntouchedNo reply, and no later commit touched the file.
Illustration: Two threads on #612 with their states.

#Likely addressed is a guess

Limn cannot know that a commit fixed what a comment asked for. It knows only that someone changed the same file after the comment. The change may be unrelated, or a rebase. So Limn calls it Likely addressed, never "addressed", and a thread in this state still counts as not resolved on GitHub.

How sure Limn is

Where it can, Limn grades a Likely addressed thread:

  • High: GitHub marked the commented lines as outdated and a later commit touched them, or the bot that wrote the comment confirmed or resolved it.
  • Medium: one sign of change, either a later commit to the file or GitHub marking the lines outdated.
  • Low: only a reply, with no change found.

With the AI features on, a review can also judge whether each thread was really addressed. See Check threads.

#Where the states are used

  • Unanswered threads lists Untouched threads older than a day.
  • A thread you started that becomes Likely addressed puts a card in My turn, so you can check the fix.
  • The Threads tab groups threads by file with their states.
  • The Threads filter narrows the Timeline by state.