<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/22/2016 06:44 PM, Max Andersen
wrote:<br>
</div>
<blockquote
cite="mid:CAHL=7VvBKm_Yfvi0qEfxRuYwEprdqBO25knt6iPREY0gs-6x_g@mail.gmail.com"
type="cite">Well we could remove all push rights to master repos
and let the ci bot do the merge.</blockquote>
You mean a CI bot that would merge on developer request? If so I
don't get how it's better than leaving the developer push directly.<br>
<blockquote
cite="mid:CAHL=7VvBKm_Yfvi0qEfxRuYwEprdqBO25knt6iPREY0gs-6x_g@mail.gmail.com"
type="cite">
<div>Then it's as prevented as gerrit. <br>
</div>
</blockquote>
Usually, Gerrit UI simply hides the "Submit" button on a
contribution if it doesn't conform to project requirements
(fast-forward, Verified+1, Code-Review+2, no -1). AFAIK, there is no
way to add such logic on GitHub UI and the Merge button is always
there, even when no-one likes it.<br>
<br>
Note that usually with Gerrit, it's still possible for committers to
push directly to master.<br>
But indeed, some projects do lock master and only allow submission
via Gerrit UI. Would GitHub allow that? Would it be good to use it
given the limitation explained above (no way to control the
availability of the merge operation in UI) ?<br>
<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>