)]}'
{
  "commit": "17c13069b47e64fb3fdd4de57f87b80943be1e4d",
  "tree": "7b563dfb8dae82d8273e74fd25a9b6828165cc10",
  "parents": [
    "d98273ba77e1ab9ec755576bc86c716a97bf59d7"
  ],
  "author": {
    "name": "Johannes Schindelin",
    "email": "johannes.schindelin@gmx.de",
    "time": "Wed Oct 07 08:17:49 2020 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Oct 07 09:54:53 2020 -0700"
  },
  "message": "GitHub workflow: automatically follow minor updates of setup-msbuild\n\nIt is the custom to follow minor updates of GitHub Actions\nautomatically, by using the suffix `@v1`. Actions\u0027 maintainers will then\nupdate that `v1` ref to point to the newest.\n\nHowever, for `microsoft/setup-msbuild`, 889cacb6897 (ci: configure\nGitHub Actions for CI/PR, 2020-04-11) uses a very specific `@v1.0.0`\nsuffix.\n\nIn this instance, that is a problem: should `setup-msbuild` release a\nnew version that intends to fix a critical bug, we won\u0027t know it, and we\nwon\u0027t use it.\n\nSuch a scenario is not theoretical. It is happening right now:\nhttps://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands\n\nLet\u0027s simplify our setup, allowing us to benefit from automatically\nusing the newest v1.x.\n\nSigned-off-by: Johannes Schindelin \u003cjohannes.schindelin@gmx.de\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fcfd138ff1833bcad3c34113f6de10809739e5d2",
      "old_mode": 33188,
      "old_path": ".github/workflows/main.yml",
      "new_id": "14ff94dcbe346d762924e1bfae556bc5c07bd863",
      "new_mode": 33188,
      "new_path": ".github/workflows/main.yml"
    }
  ]
}