<div dir="ltr">Some times a conflict resolution is required when merging forward, so we would need to make sure that non-fast-forward case is handled.<div><br></div><div>Michael</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 4, 2016 at 11:48 AM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It would still allow for merge forwards I think because:<br>
<br>
- The merge forward would happen locally (github can't stop that)<br>
- The pushes would be fast-forward which our protected branch policy allows.<br>
<br>
That's what I expect at least.<br>
<br>
-Brian<span class=""><br>
<br>
<br>
On 10/04/2016 11:45 AM, Michael Hrivnak wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Big +1 to using the review feature.<br>
<br>
Although like Austin, I really like seeing in the PR list which have<br>
been LGTM'd. Maybe it's worth not having that anymore as the price for<br>
using the review feature, but it would be a shame to lose.<br>
<br>
On mixing this with the protected branch feature, that sounds good.<br>
Would that still allow merging forward? For example, if I have a PR to<br>
2.10-dev that's been reviewed and approved, once I merge it to 2.10-dev,<br>
can I merge that change to master and push the master branch?<br>
<br>
Michael<br>
<br>
On Tue, Oct 4, 2016 at 11:06 AM, Austin Macdonald <<a href="mailto:amacdona@redhat.com" target="_blank">amacdona@redhat.com</a><br></span><span class="">
<mailto:<a href="mailto:amacdona@redhat.com" target="_blank">amacdona@redhat.com</a>>> wrote:<br>
<br>
<br>
<br>
    On 10/03/2016 05:43 PM, Sean Myers wrote:<br>
    > Github's new review feature is supported by another new github feature,<br>
    > protected branches. If wanted to, we could combine the two ideas, and<br>
    > only push to protected branches if there is at least one approved review<br>
    > and no review with required changes outstanding.<br>
    ><br>
    > I think this could be used instead of the "LGTM" label<br>
    I don't disagree, but I do like being able to see whether a PR has been<br>
    approved or not at a glance in the PR list.<br>
    > , and can also help<br>
    > with the notion of "drive-by" reviews, since the UI gives you a clear<br>
    > distinction between comments that require changes to be made and comments<br>
    > that do not require changes to be made.<br>
    ><br>
    > For reference:<br>
    > <a href="https://help.github.com/articles/about-pull-request-reviews/" rel="noreferrer" target="_blank">https://help.github.com/articl<wbr>es/about-pull-request-reviews/</a><br>
    <<a href="https://help.github.com/articles/about-pull-request-reviews/" rel="noreferrer" target="_blank">https://help.github.com/artic<wbr>les/about-pull-request-reviews<wbr>/</a>><br>
    ><br>
    > Since we've already got support for protected branches, I propose we<br>
    > enable required reviews, and stop using the LGTM label.<br>
    ><br>
    ><br>
    ><br>
    > ______________________________<wbr>_________________<br>
    > Pulp-dev mailing list<br></span>
    > <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>><br>
    > <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><span class=""><br>
    <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailma<wbr>n/listinfo/pulp-dev</a>><br>
<br>
<br>
<br>
    ______________________________<wbr>_________________<br>
    Pulp-dev mailing list<br></span>
    <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>><br>
    <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><span class=""><br>
    <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailma<wbr>n/listinfo/pulp-dev</a>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
</div></div></blockquote></div><br></div>