)]}'
{
  "commit": "41c3ad1d584f3b81bacc59e89e022dc1e7ffc3f2",
  "tree": "febd7ee67889ef5714c4cf930e32cc2a4c636dd3",
  "parents": [
    "f975f914312b258f84957d19f96014c3edd12644"
  ],
  "author": {
    "name": "Saša Živkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Fri Apr 05 17:32:14 2024 +0200"
  },
  "committer": {
    "name": "Saša Živkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Fri Apr 05 17:36:39 2024 +0200"
  },
  "message": "Resolve relative hooks.path against $site_path, not cwd of the process\n\nWhen hooks.path was given as relative path it got resolved against the\ncurrent working directory of the Gerrit process. While it may often be\nthe case that the current working directory of Gerrit process is the\n$site_path, it is not guaranteed and, depending how Gerrit is started,\nit may be some other directory. Most, if not all, of the relative paths\nin gerrit.config are resolved against the $site_path and we should do\nthe same for the hooks.path.\n\nRelease-Notes: Resolve relative hooks.path against $site_path\nChange-Id: Ie72c0657393e1dfe078155e27edbd4c0412892e6\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f415e90c3a42e75d4c9398b3fb63de16a82bc8fa",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/hooks/HookFactory.java",
      "new_id": "ea69cfcb9c685a5e3308545d5f49c589688e2bb1",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/hooks/HookFactory.java"
    },
    {
      "type": "modify",
      "old_id": "2aea5669e2e7d7bb0613469f6e1330ec692b8f00",
      "old_mode": 33188,
      "old_path": "src/main/resources/Documentation/config.md",
      "new_id": "c5698befb38ff471bf495f61a3c079f58432c4b4",
      "new_mode": 33188,
      "new_path": "src/main/resources/Documentation/config.md"
    }
  ]
}