Cherry picking should happen in the background
Right now it seems that cherry-picking a merge request happens in-request. This is going to be problematic for large merge requests or setups with a slow storage device. To work around this we should handle the cherry-picking in a Sidekiq worker. The tricky part here is handling the case where a user decides to create a merge request instead of directly picking a commit into a branch as this isn't something you can do in the background easily (as you'd have no place to be redirected to).
Any thoughts?