tree db1926aa4b237ec8e8e3a3a2af7b06ac2c874c1f
parent f4c78d9f6bb318e4b8acac9cb6b9e80dba820a54
author Marcin Czech <maczech@gmail.com> 1688155741 +0200
committer Marcin Czech <maczech@gmail.com> 1689018352 +0200

Preserve refs order in the GitBatchRefUpdateEvent event

Change I79eefbee introduced the concept of the single event
representing batch ref update. However this new event doesn't
preserve original order of the updated refs. This impacts event
consumers behaviour and can cause failures. For example if meta
ref is processed before patchset ref indexing operation will
fail because of the missing patchset.

To make sure that refs order is preserved and backward compatibility
is kept use LinkedHashSet instead of HashSet.

Bug: Issue 289321387
Release-Notes: Preserve refs order in the GitBatchRefUpdateEvent event
Change-Id: I198d60bb172edbccce739054da93e9f014c02c2b