11dd9d6e1f
Previously, we just fetched the latest commit for the given branch when presenting the resulting commit, but because something could have been committed to that branch between the time we cherry-picked and the time we render the result, the wrong commit could have been presented. Now, we fetch the commit object with the commit SHA returned by the commit change service, which should always be the correct commit. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53773
5 lines
94 B
YAML
5 lines
94 B
YAML
---
|
|
title: Resolve possible cherry pick API race condition
|
|
merge_request:
|
|
author:
|
|
type: fixed
|