{
    "content": [
        {
            "type": "text",
            "text": "# git-request-pull (man)\n\n## NAME\n\ngit-request-pull - Generates a summary of pending changes\n\n## SYNOPSIS\n\ngit request-pull [-p] <start> <url> [<end>]\n\n## DESCRIPTION\n\nGenerate a request asking your upstream project to pull changes into their tree. The request,\nprinted to the standard output, begins with the branch description, summarizes the changes\nand indicates from where they can be pulled.\n\n## TLDR\n\n> Generate a request asking the upstream project to pull changes into its tree.\n\n- Produce a request summarizing the changes between the v1.1 release and a specified branch:\n  `git request-pull {{v1.1}} {{https://example.com/project}} {{branch_name}}`\n- Produce a request summarizing the changes between the v0.1 release on the `foo` branch and the local `bar` branch:\n  `git request-pull {{v0.1}} {{https://example.com/project}} {{foo:bar}}`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (1 subsections)\n- **EXAMPLES**\n- **GIT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "git-request-pull",
        "section": "",
        "mode": "man",
        "summary": "git-request-pull - Generates a summary of pending changes",
        "synopsis": "git request-pull [-p] <start> <url> [<end>]",
        "tldr_summary": "Generate a request asking the upstream project to pull changes into its tree.",
        "tldr_examples": [
            {
                "description": "Produce a request summarizing the changes between the v1.1 release and a specified branch",
                "command": "git request-pull {{v1.1}} {{https://example.com/project}} {{branch_name}}"
            },
            {
                "description": "Produce a request summarizing the changes between the v0.1 release on the `foo` branch and the local `bar` branch",
                "command": "git request-pull {{v0.1}} {{https://example.com/project}} {{foo:bar}}"
            }
        ],
        "tldr_source": "official",
        "flags": [
            {
                "flag": "-p",
                "long": null,
                "arg": null,
                "description": "Include patch text in the output. <start> Commit to start at. This names a commit that is already in the upstream history. <url> The repository URL to be pulled from. <end> Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled. When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the <local>:<remote> syntax, to have its local name, a colon :, and its remote name."
            }
        ],
        "examples": [
            "Imagine that you built your work on your master branch on top of the v1.0 release, and want",
            "it to be integrated to the project. First you push that change to your public repository for",
            "others to see:",
            "git push https://git.ko.xz/project master",
            "Then, you run this command:",
            "git request-pull v1.0 https://git.ko.xz/project master",
            "which will produce a request to the upstream, summarizing the changes between the v1.0",
            "release and your master, to pull it from your public repository.",
            "If you pushed your change to a branch whose name is different from the one you have locally,",
            "e.g.",
            "git push https://git.ko.xz/project master:for-linus",
            "then you can ask that to be pulled with",
            "git request-pull v1.0 https://git.ko.xz/project master:for-linus"
        ],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 8,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 1,
                "subsections": [
                    {
                        "name": "-p",
                        "lines": 16,
                        "flag": "-p"
                    }
                ]
            },
            {
                "name": "EXAMPLES",
                "lines": 22,
                "subsections": []
            },
            {
                "name": "GIT",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "git-request-pull - Generates a summary of pending changes\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "git request-pull [-p] <start> <url> [<end>]\n\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Generate a request asking your upstream project to pull changes into their tree. The request,\nprinted to the standard output, begins with the branch description, summarizes the changes\nand indicates from where they can be pulled.\n\nThe upstream project is expected to have the commit named by <start> and the output asks it\nto integrate the changes you made since that commit, up to the commit named by <end>, by\nvisiting the repository named by <url>.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "",
                "subsections": [
                    {
                        "name": "-p",
                        "content": "Include patch text in the output.\n\n<start>\nCommit to start at. This names a commit that is already in the upstream history.\n\n<url>\nThe repository URL to be pulled from.\n\n<end>\nCommit to end at (defaults to HEAD). This names the commit at the tip of the history you\nare asking to be pulled.\n\nWhen the repository named by <url> has the commit at a tip of a ref that is different\nfrom the ref you have locally, you can use the <local>:<remote> syntax, to have its local\nname, a colon :, and its remote name.\n",
                        "flag": "-p"
                    }
                ]
            },
            "EXAMPLES": {
                "content": "Imagine that you built your work on your master branch on top of the v1.0 release, and want\nit to be integrated to the project. First you push that change to your public repository for\nothers to see:\n\ngit push https://git.ko.xz/project master\n\nThen, you run this command:\n\ngit request-pull v1.0 https://git.ko.xz/project master\n\nwhich will produce a request to the upstream, summarizing the changes between the v1.0\nrelease and your master, to pull it from your public repository.\n\nIf you pushed your change to a branch whose name is different from the one you have locally,\ne.g.\n\ngit push https://git.ko.xz/project master:for-linus\n\nthen you can ask that to be pulled with\n\ngit request-pull v1.0 https://git.ko.xz/project master:for-linus\n",
                "subsections": []
            },
            "GIT": {
                "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1                                   02/26/2026                          GIT-REQUEST-PULL(1)",
                "subsections": []
            }
        }
    }
}