initialize-developer-trust-profile

Initialize Developer Trust Profile

Bootstraps a developer trust profile by processing the last N PRs authored by a developer across all repositories visible to gh (not a single repo), delegating each one to /developer-trust-profile. Samples both merged and rejected PRs to avoid survivorship bias, and derives the outcome from actual review data rather than assuming all merged PRs are clean approvals.

Optionally pass --orgs followed by one or more GitHub organization logins to restrict results to PRs in repos owned by those orgs (or use multiple --owner flags in the commands below). Omit --orgs to consider PRs in any repo the token can access.

Prerequisites

• gh CLI authenticated with read access to the repositories you expect to search (public repos work without extra scope; private repos need appropriate token access)
• $1: GitHub username of the developer
• $2 (optional): number of PRs to scan (default: 10). Must be a positive integer if provided.
• --orgs (optional): one or more organization names; only PRs under those orgs are included

Workflow

Resolve arguments
      |
Build optional --owner flags from org list
      |
Fetch merged PRs + closed-without-merge PRs (global or org-scoped)
      |
Merge, sort by date, take most recent N
      |
Any PRs found?
  /         \
No            Yes
 |             |
Stop       For each PR (oldest first):
               |
           Fetch reviews
               |
           Determine outcome
           (approved / not_approved)
               |
           /developer-trust-profile
           {username} --after-review
           {repo} {pr_number} {outcome}
              |
           Report summary

Steps

1. Resolve arguments

• GITHUB_USERNAME: first positional argument
• COUNT: second positional if it is a positive integer, otherwise default 10
• ORGS: empty unless --orgs appears; every token after --orgs until the end of the argument list is an organization login (e.g. acme-corp, myorg)