{
    "content": [
        {
            "type": "text",
            "text": "# GIT-UPLOAD-ARCHIVE (man)\n\n## NAME\n\ngit-upload-archive - Send archive back to git-archive\n\n## SYNOPSIS\n\ngit upload-archive <directory>\n\n## DESCRIPTION\n\nInvoked by git archive --remote and sends a generated archive to the other end over the Git\nprotocol.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **SECURITY**\n- **OPTIONS**\n- **GIT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "GIT-UPLOAD-ARCHIVE",
        "section": "",
        "mode": "man",
        "summary": "git-upload-archive - Send archive back to git-archive",
        "synopsis": "git upload-archive <directory>",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 7,
                "subsections": []
            },
            {
                "name": "SECURITY",
                "lines": 25,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "GIT",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "git-upload-archive - Send archive back to git-archive\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "git upload-archive <directory>\n\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Invoked by git archive --remote and sends a generated archive to the other end over the Git\nprotocol.\n\nThis command is usually not invoked directly by the end user. The UI for the protocol is on\nthe git archive side, and the program pair is meant to be used to get an archive from a\nremote repository.\n",
                "subsections": []
            },
            "SECURITY": {
                "content": "In order to protect the privacy of objects that have been removed from history but may not\nyet have been pruned, git-upload-archive avoids serving archives for commits and trees that\nare not reachable from the repository’s refs. However, because calculating object\nreachability is computationally expensive, git-upload-archive implements a stricter but\neasier-to-check set of rules:\n\n1. Clients may request a commit or tree that is pointed to directly by a ref. E.g., git\narchive --remote=origin v1.0.\n\n2. Clients may request a sub-tree within a commit or tree using the ref:path syntax. E.g.,\ngit archive --remote=origin v1.0:Documentation.\n\n3. Clients may not use other sha1 expressions, even if the end result is reachable. E.g.,\nneither a relative commit like master^ nor a literal sha1 like abcd1234 is allowed, even\nif the result is reachable from the refs.\n\nNote that rule 3 disallows many cases that do not have any privacy implications. These rules\nare subject to change in future versions of git, and the server accessed by git archive\n--remote may or may not follow these exact rules.\n\nIf the config option uploadArchive.allowUnreachable is true, these rules are ignored, and\nclients may use arbitrary sha1 expressions. This is useful if you do not care about the\nprivacy of unreachable objects, or if your object database is already publicly available for\naccess via non-smart-http.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "<directory>\nThe repository to get a tar archive from.\n",
                "subsections": []
            },
            "GIT": {
                "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1                                   02/26/2026                        GIT-UPLOAD-ARCHIVE(1)",
                "subsections": []
            }
        }
    }
}