Select correct merge method for Github
Starting with Github Enterprise 3.8[0] and github.com from September 2022 on[1], the merge strategy changed from using merge-recursive to merge-ort[0]. The merge-ort strategy is available in the Git client since version 2.33.0 and became the default in 2.34.0[2]. If not configured otherwise, we've so far used the default merge strategy of the Git client (which varies depending on the client version). With this change, we are now explicitly choosing the default merge strategy based on the Github version. This way, we can reduce errors resulting from the use of different merge strategies in Zuul and Github. Since the newly added merge strategies must be understood by the mergers we also need to bump the model API version. [0] https://docs.github.com/en/enterprise-server@3.8/admin/release-notes [1] https://github.blog/changelog/2022-09-12-merge-commits-now-created-using-the-merge-ort-strategy/ [2] https://git-scm.com/docs/merge-strategies#Documentation/merge-strategies.txt-recursive Change-Id: I354a76fa8985426312344818320980c67171d774
This commit is contained in:
@@ -14,4 +14,4 @@
|
||||
|
||||
# When making ZK schema changes, increment this and add a record to
|
||||
# doc/source/developer/model-changelog.rst
|
||||
MODEL_API = 17
|
||||
MODEL_API = 18
|
||||
|
||||
Reference in New Issue
Block a user