? Failure

User tests: Successful: Unsuccessful:

avatar Kubik-Rubik
Kubik-Rubik
29 Mar 2016

Reverts joomla/joomla-cms#9580

This PR will go into 3.5.2 - I've merged into RC state, my fault. Sorry!

avatar Kubik-Rubik Kubik-Rubik - open - 29 Mar 2016
avatar Kubik-Rubik Kubik-Rubik - change - 29 Mar 2016
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 29 Mar 2016
Labels Added: ?
avatar Kubik-Rubik Kubik-Rubik - reference | 0750ba7 - 29 Mar 16
avatar Kubik-Rubik Kubik-Rubik - merge - 29 Mar 2016
avatar Kubik-Rubik Kubik-Rubik - close - 29 Mar 2016
avatar Kubik-Rubik Kubik-Rubik - change - 29 Mar 2016
Status Pending Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2016-03-29 11:44:36
Closed_By Kubik-Rubik
avatar Kubik-Rubik Kubik-Rubik - close - 29 Mar 2016
avatar Kubik-Rubik Kubik-Rubik - merge - 29 Mar 2016
avatar Kubik-Rubik Kubik-Rubik - head_ref_deleted - 29 Mar 2016
avatar mbabker
mbabker - comment - 29 Mar 2016

@Kubik-Rubik you can't propose and merge a PR within seconds/minutes like you apparently did here as it breaks the protected branch feature. Nothing can be pushed to master now because this PR didn't pass Travis-CI (because essentially by the time Travis-CI ran the PR job it couldn't find the merge reference). With any luck, the next PR merged will fix that, otherwise someone's going to have to disable the protected branch status on master to get it to re-sync.

avatar Kubik-Rubik
Kubik-Rubik - comment - 29 Mar 2016

@mbabker Damn, not my day... thought that a revert process has no impact on it. Thank you for the clarification.

@wilsonge Could you please trigger a merging process (when preparing the release maybe) so that it hopefully gets fixed. Sorry for the inconvenience!

Add a Comment

Login with GitHub to post a comment