)]}'
{
  "commit": "f8eadfe13759cbc383e698c99f9645e9ddc4c578",
  "tree": "0e05a870571e0b5cd58cd290fc1e0837db8fcd72",
  "parents": [
    "75bf837fad657f1d1f8e5036cec4e7b53fb3f3dc"
  ],
  "author": {
    "name": "Russ Cox",
    "email": "rsc@golang.org",
    "time": "Sat Jun 30 22:19:18 2018 -0400"
  },
  "committer": {
    "name": "Russ Cox",
    "email": "rsc@golang.org",
    "time": "Tue Jul 10 05:41:33 2018 +0000"
  },
  "message": "cmd/go/internal/modfile: add new requires to end of file\n\nThe old behavior was to add new requires to the first require statement in the file.\n\nIf there\u0027s more than one statement, though, it\u0027s more convenient for the first N-1\nto be the manually maintained ones and then have the (possibly large) auto-maintained\nblock at the end of the file, instead of putting the manually maintained statements\nafter a giant auto-maintained one.\n\nSuggested by Bryan Mills in an earlier CL, and works better for some real use cases.\n\nChange-Id: I17a1704ca459c8cb5536dc23997bbacc3cd997eb\nReviewed-on: https://go-review.googlesource.com/121859\nReviewed-by: Bryan C. Mills \u003cbcmills@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8963fc249f405beeb4d12da41d16f790013417e0",
      "old_mode": 33188,
      "old_path": "vendor/cmd/go/internal/modfile/read.go",
      "new_id": "1d81ff1ab7a326061f9352bbfe485533b6f9a5f5",
      "new_mode": 33188,
      "new_path": "vendor/cmd/go/internal/modfile/read.go"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "b88ad62916845b2b72d4eef9a49ccb0215b6e3e0",
      "new_mode": 33188,
      "new_path": "vendor/cmd/go/internal/modfile/rule_test.go"
    }
  ]
}