Github website should support cherry-picking.

[mirek]

Github website should support cherry-picking by going to branch, then cherry-pick, select one or more commits and apply.

[cirosantilli]

Even more powerful with :-) #200

[mirek]

@cirosantilli maybe but the beauty of cherry-pick is that, when can be cleanly applied, it doesn't require any extra UI elements.

[larsxschneider]

Cherry picking should be used with care. If you cherry pick then you introduce the same change multiple times in your repo. If this change causes a merge conflict later on then you need to resolve the merge conflict multiple times...

[mirek]

@larsxschneider sorry I don't see what you mean, anything can "cause merge conflicts later on".

I'd like to see cherry-picking in github web ui, for commits that you choose quickly, only for commits that can be cleanly applied, with minimal UI (just picking a list of commits and applying).

It's useful because sometimes there is a hot fix for other branches but you're currently working on a project locally, ie. your web app is running and you don't want to stop server, change branches, cherry pick commits and push that - in github ui you can do it very quickly with nice autocomplete/list of recent commits that are not merged yet etc.

[TPS]

This was removed in 2012: https://github.com/blog/1091-spring-cleaning

🎩/T @klaustopher via #651 (comment)

[jimis]

+1 for cherry-picking functionality. As a maintainer, every time I merge a pull request through the UI, I have to go in the code and cherry-pick the merged commits to the stable branches. This is an ugly manual process with lots of fragile copy-pasting.

What I would expect from the UI: after having pressed the "merge" button in the pull request, a "cherry-pick individual commits" button appears with a pull-down menu "to branch xxxxxx". After the button is pressed, the commits are presented in a new window, with tick-boxes next to them: "select which commits you want to cherry-pick to branch xxxxxx".

I'll be monitoring this thread.

[mirekkukla]

At a high level, there are legit use cases for cherry-picking commits. The ones on this thread are but a few of many. That's why git introduced the concept. Unless someone wants to argue the makers of github made a mistake by doing so, it's odd that this incredibly useful - and conceptually pretty simple - functionality would be removed from github.

[jimis]

Gitlab support cherry-picking in the UI.

@github where are you?

[burlen]

Would like to see this. I'm in an airport, have only my cell, would like to use web interface to make a new branch, cherry pick a few commits off another branch and then merge these.

[MatthiasSchmalz]

3rd anniversary day is coming close. Would be great to have this fixed that day.

[HelloKitty]

Ridiculous that we still can't Cherry-Pick.