1---
 2name: collaborating-through-pr-pico-sh
 3description: Collaborates on git patches via pr.pico.sh, a minimal patchbin service. Use when submitting, reviewing, or managing patch requests, or when the user mentions pr.pico.sh, patchbin, or patch requests.
 4license: GPL-3.0-or-later
 5metadata:
 6  author: Amolith <amolith@secluded.site>
 7---
 8
 9pr.pico.sh is a patchbin where collaboration happens through `git format-patch` and `git am`. Whether you are submitting code changes or reviewing them, it all happens in code — both contributor and reviewer create commits, optionally with comments in code, and exchange them as patches rather than commenting in a web UI.
10
11## Registration
12
13If `ssh pr.pico.sh` returns a "not registered" error, stop and ask the user what they would like to register as, or if they're already registered. If they're not and provide a username, register their key with `ssh {username}@pr.pico.sh register`.
14
15## Common commands
16
17```console
18ssh pr.pico.sh pr ls --mine {repo} # also --open, --closed, --accepted
19# Display metadata for a specific PR
20ssh pr.pico.sh pr summary {id}
21ssh pr.pico.sh logs --pr {id} # also --repo {id} or your own --pubkey
22
23# Apply all patches from a PR
24ssh pr.pico.sh pr print {id} | git am -3
25
26# Print a specific patchset (rather than the whole PR)
27ssh pr.pico.sh print ps-{id}
28```
29
30The project's README.md or AGENTS.md likely mention whether the project uses pr.pico.sh and which pr.pico.sh repo it uses. If you don't already know its ID, grep for `pr.pico.sh` in the README.md, first falling back to an AGENTS.md, then a broader in-cwd search if still not found, and read surrounding lines to identify the repo ID.
31
32## Admin commands
33
34```console
35# Create a repo on pr.pico.sh
36ssh pr.pico.sh repo create {repoName}
37
38# Delete a repo and all its PRs (requires --write confirmation)
39ssh pr.pico.sh repo rm --write {repoName}
40
41# Remove a specific patchset
42ssh pr.pico.sh ps rm {patchsetID}
43```
44
45## Flows
46
47You will often be _either_ reviewing or sending patches, and the user will have made it clear which. Be sure to read the right one.
48
49- For sending patches, opening a PR, contributing upstream, or similar requests when the project uses pr.pico.sh, see [contributing.md](references/contributing.md)
50- For reviewing patches/PRs, accepting a contributor's PR, or similar, see [reviewing.md](references/reviewing.md)
51- If the project uses **jj (Jujutsu)** instead of git, read [jujutsu.md](references/jujutsu.md) first — colocation is required and must be verified before generating or applying patches