Cherry-pick any commit into any branch in the web interface

@rymai We'd have to account for conflicts, probably similarly to how we handle them in MRs, but sure.

That said, I'm not sure how useful it would be to users who aren't us.

That said, I'm not sure how useful it would be to users who aren't us.

I agree, this might be very specific to our use-case.

I think it's very cool, but future stuff (after we have merge conflict resolution). @rymai can you add it to the /direction page on the website under 'Wishlist'?

This is something that my team would find very useful as we have 3 different environments. How we solve it now is cherry-picking the commits and then opening merge requests.

@JobV Sure thing, will do!

@jkregloh Glad it would be useful for your team too!

Title changed from Add a button to cherry-pick a MR commit into another branch from the MR page to Cherry-pick MR into any branch in the web interface

Added ~123454 ~122770 labels

mentioned in merge request gitlab-com/www-gitlab-com!1408 (merged)

mentioned in commit gitlab-com/www-gitlab-com@752c7115

Thanks @rymai!

I like it. I do think other people can benefit from it too.

For example you have production branch and you want easy way to pick hotfixes without merging development branch which can bring unrelated changes.

mentioned in commit dblessing/www-gitlab-com@752c7115

I think this would be a great feature - it makes it more a patch request than a feature request.

I work on a project where this would be very useful - master, staging and production are three branches for their respective environments. This feature would streamline the hot patching process.

My guess is that for most projects that would benefit from this would appreciate being able to have predefined branch order. As an example of what I mean, for the aforementioned project, we'd like to patch master first, then staging, then production - in that order; we usually do a little integration testing in between to make sure things don't break.