)]}'
{
  "commit": "e239193b9adfd83c4a9736634b83c603b8537fcf",
  "tree": "8a076081a4c3fc98725e217aed0469802e8b4218",
  "parents": [
    "bcb279b4970bc70ddb4233b9b34d38e5df8c9294"
  ],
  "author": {
    "name": "juliexxia",
    "email": "juliexxia@google.com",
    "time": "Fri Oct 09 14:08:18 2020 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Fri Oct 09 14:09:31 2020 -0700"
  },
  "message": "Fix action conflicts from exec transition + platform mappings + starlark transition.\n\nSpecifically when a two targets under a starlark transition both nullify the effect of the starlark transition (set back to the default configuration pre-starlark transition), one through a platform mapping and one through a platform mapping + an exec transition, make sure they similarly still propagate the effects of the starlark transition (i.e. CoreOptions.transitionDirectoryNameFragment and CoreOptions.affectedByStarlarkTransition)\n\nThe dream is to actually have neither propagate the effects of the starlark transition if it\u0027s going to nullified. But figuring out when we can do this would be very complex. So for now, just ensure the behavior is the same across the board.\n\nPiperOrigin-RevId: 336362151\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "79a70fd3392bdeb1a000e1fb94e19fbcea73471b",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/devtools/build/lib/analysis/config/CoreOptions.java",
      "new_id": "364fa18833b5d31ed500fad9799c876d49abd11f",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/devtools/build/lib/analysis/config/CoreOptions.java"
    }
  ]
}
