)]}'
{
  "commit": "c44765c7db4ce3972a130a65775fc440291e0d11",
  "tree": "3ccf9b30fa437480db9d812d75daae860a7aefc6",
  "parents": [
    "6cb023a67dfb840c13fa3f7aadfc0063144e6674"
  ],
  "author": {
    "name": "Edwin Kempin",
    "email": "ekempin@google.com",
    "time": "Thu Feb 10 09:17:50 2022 +0100"
  },
  "committer": {
    "name": "Edwin Kempin",
    "email": "ekempin@google.com",
    "time": "Thu Feb 10 09:21:48 2022 +0100"
  },
  "message": "Test skipping code owner config validation when creating cherry pick via API\n\nIf a change / patch set is created via the Cherry Pick Revision 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\ncherryPickInput.allowConflicts \u003d true was set), since the conflict\nmarkers in the file will be detected as invalid content.\n\nChange I66dc4cfda in Gerrit core allows to set validation options in the\ncherry pick input that are forwarded to the CommitValidationListeners.\nThis makes it possible to skip the code owner config validation when\ncreating a change via the Cherry Pick Revision REST endpoint, by\nspecifying code-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 cherry\npick input works.\n\nSigned-off-by: Edwin Kempin \u003cekempin@google.com\u003e\nChange-Id: I1f6b2f8a3ac1c821510f7ec8e294f01d72468abf\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5291479d7d7dfdac774bfc3a8735ca56f0f5008b",
      "old_mode": 33188,
      "old_path": "javatests/com/google/gerrit/plugins/codeowners/acceptance/api/CodeOwnerConfigValidatorIT.java",
      "new_id": "130f06777ecb638f769135a200ec91c804b65e96",
      "new_mode": 33188,
      "new_path": "javatests/com/google/gerrit/plugins/codeowners/acceptance/api/CodeOwnerConfigValidatorIT.java"
    }
  ]
}