Community PRs

Outside contributors give us their time. Answer quickly, ask for one thing at a time, do the work only we can do, and make sure their name ships with their change.

An outside PR is one whose author is not a current BuilderIO org member and whose branch lives in a fork. A former teammate's PR from a branch in this repo is not one. pnpm community-prs applies exactly that test.

Commands

pnpm community-prs                       # sweep: open outside PRs, longest-waiting first
pnpm community-prs pr <number>           # what you need before handling one PR
pnpm community-prs audit --by @me        # your recent replies and how those PRs ended

The script only reads. It never comments, assigns, pushes, or merges. It needs gh signed in as a BuilderIO member with read:org, and stops rather than guess who is a member. Add --json for structured output. The sweep takes about a minute; the audit takes several.

Ownership

A BuilderIO member assigned to the PR owns it, whoever or whatever assigned them. An assignee who isn't a member doesn't stop you from taking it.

• Take a PR from the sweep with gh pr edit <n> --repo BuilderIO/agent-native --add-assignee @me before you start on it. The sweep suggests an owner from the app-owner map in review-prs; framework PRs go to whoever knows the area.
• Assigning is the claim, like 👀 on a feedback report: don't take a PR another member is assigned to. If it's overdue, ask them directly first.
• review-prs stands down on outside PRs assigned to a BuilderIO member, so once you're assigned, nobody else will move it. If you can't keep it moving, unassign yourself and tell the team.
• Do not assign PRs during a dry run or on someone else's behalf.

What you can decide