Revert button creates a new branch even if conflicts occur with the revert
I attempted to revert 53176717 using the "Revert" button but there was a conflict with the nokogiri gem. The RevertService
still pushed a new branch here:
https://gitlab.com/gitlab-org/gitlab-ce/commits/revert-53176717
If possible, I would expect that the button would check if any conflicts exist before attempting to push a new branch. I'm not sure if that's possible with rugged at the moment. It looks like that the conflict check only happens after the revert is attempted.
/cc: @rdavila