)]}'
{
  "commit": "95f24f44777e0349ae14ab896ca6f7fa1175a1d8",
  "tree": "bd9f3ee5edb35a78ffb090ed5236054cfcc20d76",
  "parents": [
    "96c191c99d5c397b5b3d804ea9a687ed98f59e3f"
  ],
  "author": {
    "name": "Antoine Musso",
    "email": "hashar@free.fr",
    "time": "Tue Nov 10 16:05:34 2020 +0100"
  },
  "committer": {
    "name": "Antoine Musso",
    "email": "hashar@free.fr",
    "time": "Mon Nov 16 09:11:57 2020 +0100"
  },
  "message": "Document how to specify multiple excludeMetrics\n\nThe documentation mentions multiple patterns can be given by repeating\nthe `excludeMetrics` setting but it was unclear to me how to proceed.\n\nThe setting is fetched using a getStringList() which comes from jgit and\nindeed one just need to repeat it. An example makes it clearer.\n\nI also thought the matching was to be done against the metric names\nexposed to Prometheus, but it is instead done against the Gerrit metric\nname (`/` separated).\n\nThe doc mentions the matching is done on the whole key, document that it\nis internally using `regex.Matcher.matches()` (and not `lookingAt()`\nwhich matches at the start of the subject).  The multiple values\nexample does use a lead carret \u0027^\u0027 which indicates matching at the start\nof metric name has to be set explicitly.\n\nChange-Id: I89fd2d4bb6523446ba54f741767336f907c800ac\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "070151fc60d62b2dbe2f25e18d2fd0de86f2ac33",
      "old_mode": 33188,
      "old_path": "src/main/resources/Documentation/config.md",
      "new_id": "6c41974eb9df32fa5d304b47f46d682e9106ccf0",
      "new_mode": 33188,
      "new_path": "src/main/resources/Documentation/config.md"
    }
  ]
}