)]}'
{
  "commit": "820132833abb0739060a84c14cf313b9ba25ed7a",
  "tree": "8d8a00fabdc7727798fc4c84193340fdc6ac1603",
  "parents": [
    "3533ae1e81fdf9aab93f1d579cddeb5c5b3a2839"
  ],
  "author": {
    "name": "Nate Bosch",
    "email": "nbosch@google.com",
    "time": "Tue Nov 10 23:36:56 2026 +0000"
  },
  "committer": {
    "name": "Nate Bosch",
    "email": "nbosch@google.com",
    "time": "Wed Nov 11 00:01:21 2026 +0000"
  },
  "message": "Discourage use of production constants in expected\n\nA common antipattern in tests is to build a complete expected instance\nof a value type for comparison with `operator \u003d\u003d`, filling in some\nfields by reading constants from the code under test. Those fields can\nnever cause a failure, and every uninteresting field must still be\npopulated. Recommend using `isA` and `TypeMatcher.having` to build a\n`Matcher` that checks only the fields that are interesting for the test.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "efcae1354c41d0ae01781488290c4f718105ba5c",
      "old_mode": 33188,
      "old_path": "pkgs/matcher/README.md",
      "new_id": "73a64d20dc617f2a9964e97fe30910707f1e7ad1",
      "new_mode": 33188,
      "new_path": "pkgs/matcher/README.md"
    }
  ]
}
