)]}'
{
  "commit": "d9e42ac908e7ec3573d69169748b3c76d00f0d9a",
  "tree": "05c8ae168c904a2d56bca0e138df124efd843dab",
  "parents": [
    "e299094e8a9b2b67abac2cdb87a9999ef191de1d"
  ],
  "author": {
    "name": "Ignas Anikevicius",
    "email": "240938+aignas@users.noreply.github.com",
    "time": "Sat Jan 13 16:03:56 2024 +0900"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Jan 13 07:03:56 2024 +0000"
  },
  "message": "chore: remove MODULE.bazel.lock and ignore it (#1680)\n\nWhen we use the latest `bazel` release in the `rules_python`\nmodule, then the lock file gets created, but I am not sure if\nwe should commit it in. Since the lock file is very useful\nfor local development as it speeds up dependency refetching,\nthis PR disables it as advised in the issue below. Whilst at\nit, the `bzlmod` example also removes it for smaller diffs\nwhen we develop extensions.\n\nSee bazelbuild/bazel#20369",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bf901e2fca59d8c196ffabee61ea128018358794",
      "old_mode": 33188,
      "old_path": ".gitignore",
      "new_id": "6da16fe456b30863274b32cac7468dbba8699258",
      "new_mode": 33188,
      "new_path": ".gitignore"
    },
    {
      "type": "delete",
      "old_id": "dbdc3b1486365a902e02a7f22302431768fa7f62",
      "old_mode": 33188,
      "old_path": "examples/bzlmod/MODULE.bazel.lock",
      "new_id": "0000000000000000000000000000000000000000",
      "new_mode": 0,
      "new_path": "/dev/null"
    }
  ]
}