)]}'
{
  "commit": "9a84a0128a79285ea84410366f4eaa9876e3b109",
  "tree": "332883f70ab7c042bfe9fb15c08fb6fb34dcea90",
  "parents": [
    "4df096f1e9f8f5f7d80bd5db560fa33492ab0a8d"
  ],
  "author": {
    "name": "Joshua Humphries",
    "email": "2035234+jhump@users.noreply.github.com",
    "time": "Thu Dec 01 09:03:45 2022 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Dec 01 09:05:42 2022 -0800"
  },
  "message": "Add custom option numbers for use by Buf (#11110)\n\nWe are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example:\n1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.)\n2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.)\n\nThe suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category.\n\nFWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers.\n\nCloses #11110\n\nCOPYBARA_INTEGRATE_REVIEW\u003dhttps://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219\nPiperOrigin-RevId: 492211135\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7b86ea2803be11e7b8a42f269bef4f90c3915a8b",
      "old_mode": 33188,
      "old_path": "docs/options.md",
      "new_id": "0dbd2def5b25e755dc4a2549a6a63d3455b4f6c1",
      "new_mode": 33188,
      "new_path": "docs/options.md"
    }
  ]
}