)]}'
{
  "commit": "a14d1c74025b350762aa3b1c1785368dd914ba95",
  "tree": "494d8cc9ae4ee9881af492b14692414d757853b8",
  "parents": [
    "ec23f6e1f4c978aad3e71cd511039cbbee631e0a"
  ],
  "author": {
    "name": "Edwin Kempin",
    "email": "ekempin@google.com",
    "time": "Fri Feb 11 13:41:13 2022 +0100"
  },
  "committer": {
    "name": "Edwin Kempin",
    "email": "ekempin@google.com",
    "time": "Fri Feb 11 13:42:38 2022 +0100"
  },
  "message": "Test skipping code owner config validation when rebasing via API\n\nIf a patch set is created via the Rebase REST\nendpoint the code owner config file validation validates any OWNERS file\nthat is touched in the commit. This validation fails if such an OWNERS\nfile contains conflicts (conflicts are possible if\nrebaseInput.allowConflicts \u003d true was set), since the conflict\nmarkers in the file will be detected as invalid content.\n\nChange If025ac253 in Gerrit core allows to set validation options in the\nrebase input that are forwarded to the CommitValidationListeners. This\nmakes it possible to skip the code owner config validation when creating\na patch set via the Rebase REST endpoint, by specifying\ncode-owners~skip-validation\u003dtrue as validation option.\n\nThis change adds a test to verify that skipping the code owner config\nvalidation by setting code-owners~skip-validation\u003dtrue in the rebase\ninput works.\n\nSigned-off-by: Edwin Kempin \u003cekempin@google.com\u003e\nChange-Id: I852391f4d3ba823056a603052dcb259bad5b97bc\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "130f06777ecb638f769135a200ec91c804b65e96",
      "old_mode": 33188,
      "old_path": "javatests/com/google/gerrit/plugins/codeowners/acceptance/api/CodeOwnerConfigValidatorIT.java",
      "new_id": "ab76995e7744fd91d809a2a96286ecf5adcc51ca",
      "new_mode": 33188,
      "new_path": "javatests/com/google/gerrit/plugins/codeowners/acceptance/api/CodeOwnerConfigValidatorIT.java"
    }
  ]
}