)]}'
{
  "commit": "fa353d7e756443fef6065b9a87af4dd60cf499b4",
  "tree": "ab8ba08b100756f5190142cc2f7960a1dca308af",
  "parents": [
    "5e6e635697e730c37d510bdd9217a233b3b52692"
  ],
  "author": {
    "name": "Geoffrey Martin-Noble",
    "email": "gcmn@google.com",
    "time": "Thu Dec 08 14:42:40 2022 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Dec 08 14:42:40 2022 -0800"
  },
  "message": "Update \u0027advance upstream forks\u0027 action to use new fine-grained tokens (#11478)\n\nGitHub has new personal access tokens that allow finer-grained controls\r\nover what can be accessed. We\u0027ve been asked to migrate to these new\r\ntokens. I\u0027ve created a new secret with such a token. I\u0027m trying it out\r\nhere first, since this workflow is not particularly critical. Once all\r\nworkflows are migrated to this token, I may duplicate it as\r\n`WRITE_ACCESS_TOKEN` and switch them all back to that, so that we can\r\nkeep the old name, but I didn\u0027t want to update the value all at once\r\nand break everything.\r\n\r\nskip-ci: Doesn\u0027t affect CI workflows.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dfdbd33812d5c9ed5f3b9d2b3cab70de7fc3c295",
      "old_mode": 33188,
      "old_path": ".github/workflows/advance_upstream_forks.yml",
      "new_id": "e8f9346b5fee832b557ef980f419e39bd0f2e781",
      "new_mode": 33188,
      "new_path": ".github/workflows/advance_upstream_forks.yml"
    }
  ]
}
