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

    Function scanMergedPR

    • Scan one merged PR's activity. MergedPRScan.pending holds the notes that still wait for the user, following these rules:

      A comment, review (non-empty body) or inline review comment counts when:

      • it is maintainer engagement in the issue-comment sense of isMaintainerEngagement (never the user, never a bot; an OWNER / MEMBER / COLLABORATOR association when one is known, for reviews and inline comments too);
      • it was posted after the user's last comment, review, inline review comment AND last commit on the PR, so anything the user already answered in words or in code drops out;
      • it was posted no earlier than MERGED_PR_NOTES_PRE_MERGE_GRACE_MS before mergedAt.

      A commit counts when it is not a merge commit, its GitHub author is a non-bot account other than the user and its author date is after both the user's last commit and the user's last comment (see scanCommits for why a maintainer's rebase does not move the user's commits). Commits are not bound to the merge time: a maintainer who pushed on top the day before merging still changed what shipped.

      Parameters

      • pr: {
            issueUrl?: string;
            mergedAt: string;
            number: number;
            openedAt?: string;
            repo: string;
            title: string;
            url: string;
        }
        • OptionalissueUrl?: string

          Issue the PR closes, parsed from the PR body (#1824).

        • mergedAt: string
        • number: number
        • OptionalopenedAt?: string

          When the PR was opened (#1461). Carried from the Search API's created_at so merge detection can persist it into the outcome ledger. Optional: digests persisted by older producers don't have it.

        • repo: string
        • title: string
        • url: string
      • activity: MergedPRActivity
      • username: string

      Returns MergedPRScan

    Settings
    Member Visibility