Consider appropriate messaging during failed automated cherry-picks
May we consider applying some details for when commits fail to be picked? When this is automated away, we, as in the Delivery team, will lose sight of this. And without providing engineers advice on what to look for, we may be in a poor situation and adding contention with developer productivity. Two examples of cherry picks of a recent RC that failed for X reason:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10981#note_161291327
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10516#note_161317054
Now keep in mind, I think the above failed due to a locally running test that might have hit the production gitlab API by accident
But I think my core question may still be valuable in the future.
We should consider potentially specifying what to look for with the cherry-picking process, which branches they should be targeting, etc...