Expand description
Review threads: fetching every thread of a PR, selecting the ones a listing asks for, and finding when a commit was pushed.
A thread’s handle is the database ID of its first comment. That is the
number in the web UI’s #discussion_r... links, and it maps to both the
GraphQL thread ID that resolving needs and the comment a reply goes under.
Threads come 100 to a page, as do the comments of each thread, and every
further page is fetched, so nothing is silently left out.
Modules§
Structs§
- Comment
- Context
- Lines of the file around a thread’s line.
- Counts
- Filter
- Which threads a listing shows.
Nonemeans “either”. - PrThreads
- A PR with every review thread, and its reviews and conversation comments when they were asked for.
- Pushed
- The commit an
@SHAnames, and when it was pushed to the PR. - Thread
Enums§
Functions§
- counts
- fetch
- Fetches a PR’s threads, and with
extraits reviews and conversation comments.Nonewhen the repository or PR does not exist. - keeps_
finding - Whether a listing’s filter keeps an Entire finding, read the way a
thread is: a stale finding is outdated, an agent’s (
agent:...) a bot’s, andsincegoes by when it was raised. Its status is chosen when the findings are fetched. - pushed_
at - Finds when
sha(a prefix of at least 4 characters) was pushed to the PR: one of its commits, or a head it had before a force-push.Errsays whyshanames no such commit. - select
- The threads (then reviews and comments) a filter keeps, in order.