git request-pull: Usage, Options & Common CI Errors

git request-pull produces a text summary asking someone to pull a published branch.

In email-based and mailing-list workflows, request-pull is how you announce that a branch is ready, including a shortlog and diffstat the maintainer can review before pulling.

What it does

git request-pull <start> <url> <end> writes a human-readable message summarizing the commits between <start> and <end> on the given URL, with a shortlog and diffstat, for a maintainer to act on.

Common usage

Terminal

git request-pull v1.0.0 https://github.com/me/repo.git feature
git request-pull origin/main https://github.com/me/repo.git HEAD
git request-pull v1.0.0 git@github.com:me/repo.git my-branch

Options

Argument	What it does
<start>	Base the maintainer already has
<url>	Public URL the commits are published at
<end>	Branch/tag to be pulled (default: HEAD)
-p	Include the patch in the output

Common errors in CI

warn: No match for commit <sha> found at <url> / "Are you sure you pushed ‘<end>’ there?" - the branch is not actually published at the URL yet; push first. The <start> reference must be a real ancestor the maintainer can resolve, or the diff range is meaningless.

Related guides

git send-email: Usage, Options & Common CI Errorsgit send-email mails patch files to reviewers over SMTP. Reference for --to, --cc, --smtp-server, and the aut… git format-patch --cover-letter: Usage, Options & Common CI Errorsgit format-patch --cover-letter adds a 0000 summary patch to a series. Reference for -o, --subject-prefix, an… git bundle: Usage, Options & Common CI Errorsgit bundle packs refs and objects into one file for offline transport. Reference for create, verify, clone, a… git shortlog: Usage, Options & Common CI Errorsgit shortlog summarizes commits grouped by author, perfect for changelogs and release notes. Reference for -s…