Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-11 Thread Matt Wilkie
Yeah that was me, good to have it in our record for how to undo also, thank you. During the long saga, someone - was it Matt? - suggested removing the > credentials helper from git so that user/pw would be required for each > push. I did that. Now that it's all working, I was able to restore

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-10 Thread Thomas Passin
During the long saga, someone - was it Matt? - suggested removing the credentials helper from git so that user/pw would be required for each push. I did that. Now that it's all working, I was able to restore the helper and I don't need to provide them each time. On Windows, here's the

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-09 Thread Matt Wilkie
> > And finally, I succeeded in pushing the latest version of VR3 to Leo's devel > branch. > Yay!! :) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-09 Thread Edward K. Ream
On Fri, May 8, 2020 at 8:18 PM Thomas Passin wrote: > And finally, I succeeded in pushing the latest version of VR3 to Leo's devel > branch. > > Thanks so much to Matt and everyone who helped get this straightened out. > I second the thanks to Matt. Edward -- You received this message

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-08 Thread Thomas Passin
And finally, I succeeded in pushing the latest version of VR3 to Leo's devel branch. Thanks so much to Matt and everyone who helped get this straightened out. The main changes to VR3 were to correctly find executables like asciidoc3 that were not getting found on Windows. It turns out that

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-08 Thread Thomas Passin
On Friday, May 8, 2020 at 10:56:25 AM UTC-4, Edward K. Ream wrote: > > > > On Fri, May 8, 2020 at 8:49 AM Thomas Passin > wrote: > > After cruising through some of the settings for repo on Github, I see that >> there is a branch protection rule on the devel branch. It requires CI as a >>

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-08 Thread Edward K. Ream
On Fri, May 8, 2020 at 8:49 AM Thomas Passin wrote: After cruising through some of the settings for repo on Github, I see that > there is a branch protection rule on the devel branch. It requires CI as a > status check before merging. I don't know how to work with that in terms > of pushing

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-08 Thread Thomas Passin
On Friday, May 8, 2020 at 2:36:47 AM UTC-4, Matt Wilkie wrote: > > Thomas I made some more Leo Editor org and member changes. Please try > pushing again, with a new file that doesn't already exist in the repo. > > -matt > I created a new branch tbp-test in the Leo repo. I fetched it and

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-08 Thread Matt Wilkie
Thomas I made some more Leo Editor org and member changes. Please try pushing again, with a new file that doesn't already exist in the repo. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

2020-05-06 Thread Matt Wilkie
hmmm, not sure what's going on here. How about try adding a new file that will have no prior history. It can be a blank do nothing thing that we remove later. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and