)]}'
{
  "commit": "b3abc506133e83d3d9dc972d29710333a57a1fff",
  "tree": "ef42f924df4fa7b97a46321024a0093e1ac8c0f6",
  "parents": [
    "75d14d35e06a48891b0c41745c3f34cee8c6415a"
  ],
  "author": {
    "name": "Oliver Newman",
    "email": "olivernewman@fuchsia.infra.roller.google.com",
    "time": "Wed Jun 18 13:48:46 2025 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Jun 18 13:51:35 2025 -0700"
  },
  "message": "[roll] Roll infra/recipes [cherry_pick] Use integration repo if remote matches\n\nThis is a quick fix for failures like this:\nhttps://screenshot.googleplex.com/4KZyzSGkoffcojD\n\nThat happens when trying to cherry-pick a smart-integration CL onto a\nnon-\"sd\" branch, in this case \"canary\". We use the branch name to\ndetermine which integration repo to cherry-pick the change into, so if\nthe branch name doesn\u0027t contain \"sd\" then we\u0027ll fall back to using GI,\nwhich is incorrect.\n\nAs a workaround, use an integration repo for the checkout if it matches\nthe remote of the incoming CL. This doesn\u0027t handle non-integration repos\nlike smart.git, but cherry-picks in smart.git on non-milestone branches\nshould be rare compared to cherry-picks in integration repos.\n\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1304486\nOriginal-Revision: 2c2c500c5ee3292e78f5ba980973be9bdb25a6d1\nGitOrigin-RevId: 197ce2524d34214f0e861fbec7e2557a1ba1624b\nChange-Id: Ia161c8f1126bd1418fb5b751f2d6eaef85271c8d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e42170c56d5178f04a424bc950ae8e05a223c787",
      "old_mode": 33188,
      "old_path": "infra/recipes",
      "new_id": "5bb03d3453c1ece3860b03451f3091245e76daed",
      "new_mode": 33188,
      "new_path": "infra/recipes"
    }
  ]
}