)]}'
{
  "commit": "f836fe6eb49c820e2599547b02aecd43206403d5",
  "tree": "8c27c0839bb4a4a6539078d4609f9dcc12a5056e",
  "parents": [
    "f352bcdd05a0e498af6bcb3e715a6fec830adfc5"
  ],
  "author": {
    "name": "Corentin Kerisit",
    "email": "corentin.kerisit@gmail.com",
    "time": "Fri Nov 14 22:24:24 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Nov 14 22:24:24 2025 +0100"
  },
  "message": "Transition request_nogo to False for cgo_context_data (#4512)\n\nThis is to avoid cc toolchain dependencies in different configurations.\n\nI feel this is fine since `cgo_context_data` only calls cc toolchain\nAPIs.\n\nThe specific case which triggered this PR is\nhttps://github.com/cerisier/toolchains_llvm_bootstrapped/issues/45#issuecomment-3533067960\nwhere paths provided by CC toolchain would end up being included\nmultiple times in the linker invocation but with different\nconfiguration-specific output directory, one of which was non existent\nin the linker action sandbox.\n\nLooking at the difference between the 2 configurations shows:\n```\nFragmentOptions user-defined {\n  @@rules_go+//go/private:request_nogo: null, true\n}\n```\n\nwhich felt non necessary for CGO CC toolchain dependencies.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "eb9491cb8b68422840c46e9f4b5fd8533f6cc1c7",
      "old_mode": 33188,
      "old_path": "go/private/context.bzl",
      "new_id": "1e16e890dc0ffd5b5eef7fd70ab62c3f2323f3e4",
      "new_mode": 33188,
      "new_path": "go/private/context.bzl"
    },
    {
      "type": "modify",
      "old_id": "c4b1092dc2e1ca93a658507c9565cf45d8ecabdd",
      "old_mode": 33188,
      "old_path": "go/private/rules/transition.bzl",
      "new_id": "b31a29aa350db5cf98f75c3f7a30b103bc1b155b",
      "new_mode": 33188,
      "new_path": "go/private/rules/transition.bzl"
    }
  ]
}
