)]}'
{
  "commit": "68cb0b5253a05d62adc5cf6c0a60dc58038b546e",
  "tree": "d63ccd3982a051c84e037cc920ad3a248fee5da2",
  "parents": [
    "95262afe788e0b6b4ae5ff37e8d28fb5883c1a82"
  ],
  "author": {
    "name": "Justin Tobler",
    "email": "jltobler@gmail.com",
    "time": "Tue May 20 11:32:18 2025 -0500"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue May 20 11:43:36 2025 -0700"
  },
  "message": "builtin/receive-pack: add option to skip connectivity check\n\nDuring git-receive-pack(1), connectivity of the object graph is\nvalidated to ensure that the received packfile does not leave the\nrepository in a broken state. This is done via git-rev-list(1) and\nwalking the objects, which can be expensive for large repositories.\n\nGenerally, this check is critical to avoid an incomplete received\npackfile from corrupting a repository. Server operators may have\nadditional knowledge though around exactly how Git is being used on the\nserver-side which can be used to facilitate more efficient connectivity\ncomputation of incoming objects.\n\nFor example, if it can be ensured that all objects in a repository are\nconnected and do not depend on any missing objects, the connectivity of\nnewly written objects can be checked by walking the object graph\ncontaining only the new objects from the updated tips and identifying\nthe missing objects which represent the boundary between the new objects\nand the repository. These boundary objects can be checked in the\ncanonical repository to ensure the new objects connect as expected and\nthus avoid walking the rest of the object graph.\n\nGit itself cannot make the guarantees required for such an optimization\nas it is possible for a repository to contain an unreachable object that\nreferences a missing object without the repository being considered\ncorrupt.\n\nIntroduce the --skip-connectivity-check option for git-receive-pack(1)\nwhich bypasses this connectivity check to give more control to the\nserver-side. Note that without proper server-side validation of newly\nreceived objects handled outside of Git, usage of this option risks\ncorrupting a repository.\n\nSigned-off-by: Justin Tobler \u003cjltobler@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "20aca92073d8c9d65fc78ce5f3f48a02239333f5",
      "old_mode": 33188,
      "old_path": "Documentation/git-receive-pack.adoc",
      "new_id": "0956086d6117d3dbcd4e68651b53e692716cd067",
      "new_mode": 33188,
      "new_path": "Documentation/git-receive-pack.adoc"
    },
    {
      "type": "modify",
      "old_id": "c92e57ba188a196e9b6d18c1ede5e76fbf8c0b33",
      "old_mode": 33188,
      "old_path": "builtin/receive-pack.c",
      "new_id": "a317d6c278de2174db2ee7d5d782ede4f7331944",
      "new_mode": 33188,
      "new_path": "builtin/receive-pack.c"
    },
    {
      "type": "modify",
      "old_id": "9afea54a2678ba2866e874a81ad0ec9fa6473461",
      "old_mode": 33261,
      "old_path": "t/t5410-receive-pack.sh",
      "new_id": "f76a22943ef0d1787cc82bc4655e91b8bbaa5d15",
      "new_mode": 33261,
      "new_path": "t/t5410-receive-pack.sh"
    }
  ]
}