<div dir="ltr"><div>Hi Floris,</div><div dir="ltr"><div><br></div>> <span style="font-size:13.1999998092651px;line-height:19.7999992370605px">What happens to existing pull requests? If we don't merge them before</span><br style="font-size:13.1999998092651px;line-height:19.7999992370605px"><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">> Sat we have to convert them to git ourself and re-make the PR?</span><br><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"><br></span></div></div><div dir="ltr"><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">Yes, as there are few PRs and there's no automatic way to do migrate them, I think that is a reasonable approach. For PRs that; </span><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">we should ask submitters to open new PRs in GitHub after the conversion.</span><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"> </span></div></div><div dir="ltr"><div><br></div><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">> But for #296 I'm preparing a PR at</span><br style="font-size:13.1999998092651px;line-height:19.7999992370605px">> <a href="https://bitbucket.org/flub/pytest-py35" rel="noreferrer" style="font-size:13.1999998092651px;line-height:19.7999992370605px" target="_blank">https://bitbucket.org/flub/pytest-py35</a><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"> (because it needed to be</span><br style="font-size:13.1999998092651px;line-height:19.7999992370605px"><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">> rebased onto pytest-2.7). I think I'd prefer to merge that before the</span><br style="font-size:13.1999998092651px;line-height:19.7999992370605px"><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">> conversion even if not all tests are fixed by Sat (but hopefully they</span><br style="font-size:13.1999998092651px;line-height:19.7999992370605px"><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">> will be!). Does that sound reasonable?</span><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"><br></span></div><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"><br></span></div></div><div dir="ltr"><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">IMO yes, unless others disagree.</span></div><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"><br></span></div><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px">Cheers,</span></div><div><span style="font-size:13.1999998092651px;line-height:19.7999992370605px"><br></span></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jun 10, 2015 at 8:47 PM Floris Bruynooghe <<a href="mailto:flub@devork.be" target="_blank">flub@devork.be</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10 June 2015 at 14:07, Bruno Oliveira <<a href="mailto:nicoddemus@gmail.com" target="_blank">nicoddemus@gmail.com</a>> wrote:<br>
> Hi guys,<br>
><br>
> Just wanted to know if everyone is OK with migrating pytest to GitHub this<br>
> Saturday (June 13th).<br>
> If all agree, I will send an email Saturday when I start the migration<br>
> process (issues + repository), meanwhile no one should commit to BitBucket<br>
> until the process is complete.<br>
<br>
What happens to existing pull requests? If we don't merge them before<br>
Sat we have to convert them to git ourself and re-make the PR?<br>
<br>
I think I'm happy to decline #271 and #292.<br>
But for #296 I'm preparing a PR at<br>
<a href="https://bitbucket.org/flub/pytest-py35" rel="noreferrer" target="_blank">https://bitbucket.org/flub/pytest-py35</a> (because it needed to be<br>
rebased onto pytest-2.7). I think I'd prefer to merge that before the<br>
conversion even if not all tests are fixed by Sat (but hopefully they<br>
will be!). Does that sound reasonable?<br>
<br>
<br>
Floris<br>
_______________________________________________<br>
pytest-dev mailing list<br>
<a href="mailto:pytest-dev@python.org" target="_blank">pytest-dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/pytest-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/pytest-dev</a><br>
</blockquote></div></div>