merged Buy $MERGED

Eligibility

A merged PR takes the next-merge pot only when ALL of these hold:

  1. Merged into the repo's default branch.
  2. The author is a human: a GitHub User, not a [bot] login, not a known automation account.
  3. The author's account was at least 180 days old when it merged.
  4. Write-access review: an APPROVED review by someone who is not the author and has write access (owner, member, collaborator, or a login that has merged in that repo, or one the maintainers pinned), OR it was merged by a human who is not the author. A merge-queue merge counts only through the approval path.
  5. The author has fewer than 3 eligible PRs already allocated in that repo that UTC day.
  6. The repo is not opted out.

Self-merged PRs with no qualifying approval never pay (the maintainer pot covers that person). Reverts never pay. Public reasons on the wall: no approving review, approval without write access, approved only by its own author, bot author, author account too new, daily limit, not the default branch, opted out.

Reference PRs (recorded from GitHub)

  • anza-xyz/agave #15959: self-merged, approved by a MEMBER: passes through the approval.
  • vercel/next.js #99964: self-merged, approved by a reviewer GitHub labels CONTRIBUTOR who has merged in the repo himself (#99955): a known writer, passes.
  • microsoft/vscode #340827: self-merged, approved by a MEMBER: passes.

Data is read from GitHub's public API, read only. When review data has not been fetched yet a merge shows as "pending review data", never guessed.