@oss-autopilot/core - v3.42.2
    Preparing search index...

    Interface ReviewedPRFollowUp

    A PR the user reviewed where the author has moved the thread since.

    interface ReviewedPRFollowUp {
        author: string;
        authorComments: number;
        baseUnknown: boolean;
        commits: ReviewedPRCommit[];
        compareRange?: string;
        compareUrl?: string;
        headSha: string;
        latestActivityAt: string;
        latestCommentAt?: string;
        mergedUpstream: boolean;
        moreCommits: number;
        moreQuestions: number;
        number: number;
        prUrl: string;
        questions: ReviewedPRQuestion[];
        rebased: boolean;
        repo: string;
        reviewedAt: string;
        reviewedSha?: string;
        title: string;
    }
    Index
    author authorComments baseUnknown commits compareRange? compareUrl? headSha latestActivityAt latestCommentAt? mergedUpstream moreCommits moreQuestions number prUrl questions rebased repo reviewedAt reviewedSha? title
    author: string

    GitHub login of the PR author.

    authorComments: number

    Comments by the PR author after reviewedAt (questions included).

    baseUnknown: boolean

    The reviewed commit's place in the PR's commit list is unknown and commits were pushed since: the user's last word was a plain comment, which names no head, or (rarely) reviewedSha is known but the commit list was cut at GitHub's cap before reaching it. commits were then picked by date, which can miss a cherry-pick or rebased fix carrying an older date, and no range is offered. False when nothing was pushed or when reviewedSha was found in the list.

    commits: ReviewedPRCommit[]

    Non-merge commits by someone other than the user or a bot after the review, oldest first; capped. The commits after reviewedSha in the PR's commit list when it is known and still there, else those dated after reviewedAt.

    compareRange?: string

    <reviewedSha>...<headSha>, set only when GitHub confirmed reviewedSha is an ancestor of the head and none of rebased, mergedUpstream or baseUnknown applies, so the range shows exactly what changed since the review.

    compareUrl?: string

    github.com compare page for compareRange.

    headSha: string
    latestActivityAt: string

    Newest date among the commits and comments that qualified the PR; the dismiss stamp is compared with this. Can predate reviewedAt when the only new work is a commit carrying an old author date (cherry-pick).

    latestCommentAt?: string

    Newest comment, review or inline comment that qualified the PR (an author reply or a question for the user); absent when only commits did. A dismiss that recorded the PR's head is compared with this: with the head unchanged, only a comment after the dismiss brings the PR back.

    mergedUpstream: boolean

    A merge commit follows the reviewed one (upstream merged into the branch), so <reviewedSha>...<headSha> would include the upstream changes. No range; read the per-commit diffs of commits.

    moreCommits: number

    Commits dropped from commits by the cap.

    moreQuestions: number

    Questions dropped from questions by the cap.

    number: number
    prUrl: string
    questions: ReviewedPRQuestion[]

    Comments addressed to the user after reviewedAt, oldest first; capped.

    rebased: boolean

    The reviewed commit is gone from the PR's commit list or is no longer an ancestor of the head (force-push or rebase). There is no honest range; read commits, which were then picked by date.

    repo: string
    reviewedAt: string

    When the user last reviewed or commented on the PR.

    reviewedSha?: string

    Head SHA the user's last review or inline comment was made against (commit_id). Absent when their last word was a plain comment, which names no head; baseUnknown then says whether that matters.

    title: string

    Settings
    Member Visibility

    On This Page
    Properties