)]}'
{
  "commit": "ed1d7069d296cfa4965d44bf0d1b5b3289f2606a",
  "tree": "0e7b351785040674ca8357a97accb41eb2f159d5",
  "parents": [
    "8a6ab2b83af0e3cc87e82e504b1148d55eb9b1de"
  ],
  "author": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Wed Jul 03 18:05:30 2024 +0100"
  },
  "committer": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Wed Jul 03 18:07:24 2024 +0100"
  },
  "message": "Ignore refs/multi-site/version on global-refdb in push replication filter\n\nWhen I509dd7075b0 stopped updating the SHA1 for refs/multi-site/version\nin global-refdb in this stable-3.4 branch, it did not take into\nconsideration that existing setups may have plenty of\nrefs/multi-site/version already stored on them.\n\nStopping the update of those refs on the global-refdb had a negative\nimpact on the consistency of the replication of refs/multi-site/version\nacross the multi-site clusters, causing missed replication events.\n\nConsider the refs/multi-site/version on global-refdb as non-existent\nand skip altogether the associated checks if the associated local refs\nwere already up-to-date.\nThis change effectively ignores weather the local refs/multi-site/version\nis up-to-date or not and always pushes the refs to replication remotes.\n\nThis is the completion of the similar fix performed on the\nMultisiteReplicationFetchFilter in I8b938675.\n\nChange-Id: I833138849807475a7aed308d8703bb7e16728d2d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6f9c2e7319c7ac841edd456295170be75e01d066",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/multisite/validation/MultisiteReplicationPushFilter.java",
      "new_id": "777886d9c7fe7b7ee901a82cf7dd76a136aed73a",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/multisite/validation/MultisiteReplicationPushFilter.java"
    }
  ]
}