Last modified: 2013-11-23 12:13:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59324, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57324 - Request for disabling the "+2 triggers auto-merge" on gerrit/jenkins for all extensions maintained by user Wikinaut
Request for disabling the "+2 triggers auto-merge" on gerrit/jenkins for all ...
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-20 21:59 UTC by T. Gries
Modified: 2013-11-23 12:13 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description T. Gries 2013-11-20 21:59:50 UTC
Request for disabling the "+2 triggers auto-merge" on gerrit/jenkins for all extensions maintained by user Wikinaut

I never liked the "+2 ==> auto-merging" for my extensions. 

Can someone please switch this off for my extensions, thanks in advance, or tell me how I can disable that ?
Comment 1 Antoine "hashar" Musso (WMF) 2013-11-22 21:55:37 UTC
The workflow being used is that people use Code-Review +2 to notify the change is ready to be merged.  The automatic tests are run and if they pass, the change lands in the branch automatically.

So just vote +1 ?
Comment 2 T. Gries 2013-11-22 22:12:56 UTC
(In reply to comment #1)
> The workflow being used is that people use Code-Review +2 to notify the
> change
> is ready to be merged.  The automatic tests are run and if they pass, the
> change lands in the branch automatically.
> 
> So just vote +1 ?

Antoine, I agree with you. But it may also happen, that one accidentially clicks +2 with the consequence, that the commit is immediately merged. Perhaps it's worth to add one further confirmation window "do you really want to merge" for that case.
Comment 3 Andre Klapper 2013-11-23 10:06:36 UTC
I'm highly against "Did you really want to click what you just clicked" dialogs. plus Git offers you the chance to revert the last change.
Comment 4 T. Gries 2013-11-23 12:04:22 UTC
(In reply to comment #3)
> I'm highly against "Did you really want to click what you just clicked"
> dialogs. plus Git offers you the chance to revert the last change.

Andre, you can say what you want, freedom of speech, but I filed this issue as a personal wish, that the extensions maintained by myself are not auto-merging-on+2, respectfully stated, I wish to maintain this request (reopened).


I did not say, that it is a bug.
Comment 5 T. Gries 2013-11-23 12:05:15 UTC
We can discuss this in the chat. I am *in* now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links