)]}'
{
  "commit": "cee99c0f96fe2002e8a7c606904ece3a1d61ebd6",
  "tree": "d4925460a22511da2700120e29f92f04cdbb3db1",
  "parents": [
    "2b9d635e74e54c8475b1a0452de0ba0a7a3bc08c"
  ],
  "author": {
    "name": "Dmitri Shuralyov",
    "email": "dmitshur@golang.org",
    "time": "Fri Nov 08 13:13:23 2024 -0500"
  },
  "committer": {
    "name": "Gopher Robot",
    "email": "gobot@golang.org",
    "time": "Fri Nov 08 19:19:23 2024 +0000"
  },
  "message": "example/ivy: use tools build constraint in tools.go\n\nIn modern versions of the go command, the go mod tidy command doesn\u0027t\nconsider module requirements coming from files with an \"ignore\" build\nconstraint. Use \"tools\" instead.\n\nThis way, running go mod tidy on this module becomes a no-op, instead\nof deleting all of the requirements from go.mod and go.sum.\n\nChange-Id: I42a24c462acf7340410614fa3b0dd80608efcdaa\nReviewed-on: https://go-review.googlesource.com/c/mobile/+/626655\nReviewed-by: David Chase \u003cdrchase@google.com\u003e\nReviewed-by: Dmitri Shuralyov \u003cdmitshur@google.com\u003e\nAuto-Submit: Dmitri Shuralyov \u003cdmitshur@golang.org\u003e\nLUCI-TryBot-Result: Go LUCI \u003cgolang-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ab067c2461728f8d84506710d8640a03cf836b58",
      "old_mode": 33188,
      "old_path": "example/ivy/tools.go",
      "new_id": "de6105c527045d80ff5b9c0edafeb7c23f465dcf",
      "new_mode": 33188,
      "new_path": "example/ivy/tools.go"
    }
  ]
}