Skip to content

jouet pr land ​

  • Usage: jouet pr land [FLAGS] [PR]

Merge a PR that is ready, honouring branch protection

Refuses (exit 4) unless pr next says ready_to_merge, and says what is missing. With --update, a branch behind its base is first updated on GitHub by merging the base in (never a force-push), and its new checks are waited for. The merge goes through the API with the head SHA as a guard, the way the merge button does, so branch protection applies and is never bypassed. Then the PR is confirmed merged and the merge commit printed. It asks first only when a person is at a terminal (stdin and stderr are terminals and no coding agent is detected); anyone else must pass --yes or --dry-run, or it exits 2 before contacting GitHub.

The PR's checks on GitHub, which pr next reads, are its tests. Verify that the configured checks cover the tests the change needs.

Arguments ​

  • [PR] — The PR: a number, URL, OWNER/REPO#N or branch. Defaults to the current branch's PR

Flags ​

  • --repo <OWNER/NAME> — The repository for a bare number or branch. Defaults to the git remote
  • --method <METHOD> — How to merge: squash, merge or rebase (default squash)
  • --update — Update a branch that is behind its base by merging the base in on GitHub, then wait for its checks
  • --yes — Merge without asking
  • --dry-run — Print the plan and change nothing
  • --timeout <DUR> — How long to wait for checks after --update (default 30m)
  • --interval <DUR> — Time between the first checks of that wait; backs off to 15s (default 10s)
  • --settle <DUR> — How long to wait for GitHub to compute an unknown mergeable state (default 20s; 0 disables)
  • -h --help — Print help
MIT LicenseCopyright © 2026jdx.dev