Skip to content
  1. Wiki
  2. Basics
  3. PRs, commits and merging

PRs, commits and merging

A PR is a request: "please review these changes". Once approved, they're merged into the main branch.

An analogy

Like handing in homework. Your draft can be messy, the copy you hand in is neat, and it counts once the teacher signs off.

In pstack

By default, pstack wraps up every task as a PR. The "open a PR" playbook sorts the changes into a few small commits. It writes the title and description, then gives you the link. The author's view: five small PRs beat one big one.

Once the PR is open, the "Babysit" playbook watches it. It resolves conflicts, answers reviews and fixes the automated checks (CI). It never merges. To merge, you say "land the stack" and the "Shipping" playbook takes over.

Common misconceptions

  • "All-green CI means it's safe to merge": green doesn't mean safe. The Shipping playbook sends a different AI, one that didn't write the code, to check each PR for real. Only the ones that pass get merged.
  • "You can't use pstack without GitHub": only the PR steps need it. Changing code locally or tracking down a problem doesn't.

Try it: Full guide step 6: Verify and ship

Related: Worktrees, Verification skill

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.