)]}'
{
  "commit": "986bcc14ca19d030da571af9a83058025f250254",
  "tree": "5b60eac9a0b835860182e8b05d2aeffc51298786",
  "parents": [
    "1dd567da00eec3ccfbcbafb7a04f4297e7a69b48"
  ],
  "author": {
    "name": "Austin Clements",
    "email": "austin@google.com",
    "time": "Wed Oct 20 11:50:19 2021 -0400"
  },
  "committer": {
    "name": "Austin Clements",
    "email": "austin@google.com",
    "time": "Tue Oct 29 18:08:10 2024 +0000"
  },
  "message": "14313-benchmark-format: add unit metadata\n\nThe predefined keys differ slightly from what I proposed in golang/go#43744. I\ntried specifying {higher,lower}\u003d{better,worse} like I originally\nproposed and it just got really messy. Turning it around to\nbetter\u003d{higher,lower} means its somewhat backwards from what you might\nexpect from English phrasing, but it lets us use a single key because\nI don\u0027t think anyone is going to accidentally write\nworse\u003d{higher,lower}, and this avoids any annoying questions about\nwhat happens if a user specifies both \"higher\" and \"lower\".\n\nFor golang/go#43744.\n\nChange-Id: I895914b179c291003e76f897cabbcbdb2381f163\nReviewed-on: https://go-review.googlesource.com/c/proposal/+/357530\nReviewed-by: Michael Knyszek \u003cmknyszek@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3fb3ef747df91c5ad2ead363dc88ba834b161924",
      "old_mode": 33188,
      "old_path": "design/14313-benchmark-format.md",
      "new_id": "45944bdf4a08b32bd54d98cbdffa36614536ec26",
      "new_mode": 33188,
      "new_path": "design/14313-benchmark-format.md"
    }
  ]
}