Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- About 70 reviews to start, then about 25 a month
- Unlimited repos
git request-pull writes a pull request as text and sends nothing. You give it a commit the project already has, the URL of a repository you pushed your branch to, and the branch, and it prints a message to paste into an email: the base commit, where to fetch from, your commits by author and a diffstat.[1] It does not open a pull request on GitHub. There you open one with the Compare & pull request banner or gh pr create.[2]
HighKnown issue in the Code Review benchmark · caught by DeepSeek V4.1 FlashSee the graded case
We ran it on a two-commit branch with Git 2.50 on November 10, 2026. Before the push, it warned that the commit was not at the URL, printed the whole request anyway and exited with status 1, so a script that ignores the exit status can mail a request nobody can pull. We build IonWarp, an AI reviewer for GitHub pull requests. If your project lives on GitHub, open a pull request there, where the review, the checks and the merge happen in one place. Keep request-pull for maintainers who pull by email, as Linux's do.
$ git push fork fix-rounding
$ git request-pull v1.0 ../fork.git fix-rounding
The following changes since commit 95551fd29efda85e7ea16a0e221481ccc7080b3d:
Add cart total (2026-11-10 10:55:16 -0800)
are available in the Git repository at:
../fork.git fix-rounding
for you to fetch changes up to 96126ea90def301d3b6a8598e3240e972d1eb348:
cart: add total_cents (2026-11-10 10:55:16 -0800)
----------------------------------------------------------------
Your Name (2):
cart: sum prices as Decimal
cart: add total_cents
cart.py | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)First a commit the upstream project already has, such as a release tag. Then the URL of the repository you pushed to. Last the branch or tag to be pulled, which defaults to HEAD.[1] Ours were v1.0, a local fork and fix-rounding; a real request names a URL the maintainer can reach.
Run before the push, the same command printed "No match for commit … found at ../fork.git" and "Are you sure you pushed 'fix-rounding' there?", then the full request, and exited with status 1. After the push it printed no warning and exited 0.
With the branch left off, it fell back to HEAD and printed the same warnings, now asking whether we had pushed 'HEAD', though fix-rounding was pushed. It looks for your last commit at the fork's HEAD, and the fork's HEAD was another branch. Name the branch and the warning goes. If the branch has a different name in that repository, write both, as in fix-rounding:rounding-fix.[1]
A branch description, set with git branch --edit-description, prints above the commit list, and when you ask for a tag its message prints there instead. We tried both. The Linux kernel's guide wants that tag signed, with a message that says what the changes are, why they should be merged and how they were tested.[3]
Push to a repository the maintainer can fetch from. Linus Torvalds only accepts pull requests based on a signed tag, made with git tag -s and pushed like a branch.[3]
If it prints no warn: lines and exits with status 0, the URL has your last commit. Add -p if the maintainer wants the patch text in the message as well.[1]
Kernel maintainers send it inline, to the maintainer with the mailing list copied, under a subject such as [GIT PULL] <subsystem> changes for v4.15-rc1.[3] The maintainer then runs git pull with the URL and branch from the message.
Linux does not take them there: on November 10, 2026, torvalds/linux on GitHub said "Pull request creation is restricted" and listed none, open or closed.[4] For a project that does, push the branch and run gh pr create.[2] With IonWarp installed, its Code Review reads the diff and posts what it finds as one comment on the pull request, with the file and line it points to.
Code ReviewOn Starter, Pro and Max
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
It prints a summary of the commits you want pulled, from a commit the project already has to the end of your branch, with the URL to fetch them from, a shortlog and a diffstat. It sends nothing: you paste the text into an email.
No. It only writes text. On GitHub you open a pull request from the Compare & pull request banner after a push, or with gh pr create in a terminal.
It could not find your last commit at the URL you gave. Either the branch is not pushed yet, or you left out the branch name and it looked for HEAD there. Push, name the branch, and run it again; a clean run prints no warning and exits with status 0.
They are the two ends of one exchange. git request-pull asks a maintainer to pull your branch, and the maintainer answers by running git pull with the URL and branch the message names.
Most people who search for a request pull on GitHub mean a pull request, the page that proposes merging a branch and holds its review. In Git, request-pull is only the command that writes the request as text.
isinstance check at line 254 tests against multiprocessing.Process which is the default context's ForkProcess class, not the SpawnProcess class created by multiprocessing.get_context('spawn'), causing the check to always be False on Linux and preventing process.kill() from being called on unhealthy workers · Code Review