)]}'
{
  "commit": "55ad154c961d8326315b1c8147f4e504cd95e9e6",
  "tree": "706fdb438bffd9acfa31219993a3d3715fe49e24",
  "parents": [
    "30032b24a2224a7f6349f8ccaea23e1a2395af01"
  ],
  "author": {
    "name": "Dirk Pranke",
    "email": "dpranke@google.com",
    "time": "Mon Jan 25 13:24:43 2021 -0800"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Mon Jan 25 21:39:52 2021 +0000"
  },
  "message": "Fix bug in analyze related to sub-configs.\n\nAnalyze had a bug where if you modified a build file containing\na config that was only used as a sub-config, analyze wouldn\u0027t\nthing changes to the file would matter.\n\nThis apparently is due to sub-configs not being treated as fully\ndefined items in the builder (which is sensible), which led to\nthe analyze code not seeing them directly.\n\nA fix for this is to walk any configs that *are* defined as part\nof analyze and explicitly check them for subconfigs that might\nbe relevant.\n\nBug: 131\nChange-Id: I0323c2340ccda58b341699ed221d2fd54d9d261c\nReviewed-on: https://gn-review.googlesource.com/c/gn/+/11000\nCommit-Queue: Dirk Pranke \u003cdpranke@google.com\u003e\nReviewed-by: Brett Wilson \u003cbrettw@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "47b0a6d1d4bee19e9077da6aae60b0f06b444d68",
      "old_mode": 33188,
      "old_path": "src/gn/analyzer.cc",
      "new_id": "a42779ae5dd7c65cbcd1dc90661136228288e013",
      "new_mode": 33188,
      "new_path": "src/gn/analyzer.cc"
    },
    {
      "type": "modify",
      "old_id": "9f7d8976dfd93985a32097ba7bc49c727cd680f2",
      "old_mode": 33188,
      "old_path": "src/gn/analyzer_unittest.cc",
      "new_id": "558700e9c76cc0fd50debcab78f397d04977fb2c",
      "new_mode": 33188,
      "new_path": "src/gn/analyzer_unittest.cc"
    }
  ]
}
