Hi Nitesh,
Many thanks, I will check it in a couple of days.
Cheers,
Vlad
On Mon, 11 Sep 2017, 19:01 Turaga, Nitesh
wrote:
> Hi
>
> Your key will be added in the next run of our script. You can change your
> GitHub keys, our script will take in the new one, and
Hi
Your key will be added in the next run of our script. You can change your
GitHub keys, our script will take in the new one, and you don’t have to
resubmit on the google-form.
It is run manually at the moment at noon EST everyday.
Nitesh
> On Sep 11, 2017, at 1:12 PM, Vladimir Kiselev
Thanks Simina,
I think I've done all the steps described there before and was able to push
to upstream. I can't do it anymore and try to figure out why.
Could anyone else please help?
Cheers,
Vlad
On Mon, 11 Sep 2017, 18:03 Simina Boca wrote:
> Hi, Simina.
>
> Take a
Hi, Simina.
Take a look at the FAQ, #3, here:
http://bioconductor.org/developers/how-to/git/faq/
Have you submitted an SSH key somehow?
>
> Am I missing something here? Alternatively, I suppose I can just make the
> changes I want and simply open another issue, although it would be nice to
>
Hi Simina,
Thanks for your quick reply, but it looks like to forgot to paste your
response from Sean (at least I couldn't find it in your email).
Cheers,
Vlad
On Mon, Sep 11, 2017 at 5:58 PM Simina Boca wrote:
> Hi Vladimir,
> This seems like the same error I was
Hi Vladimir,
This seems like the same error I was getting. Here is the helpful advice I
got from Sean:
Hi, Simina.
On Mon, Sep 11, 2017 at 12:55 PM, Vladimir Kiselev <
vladimir.yu.kise...@gmail.com> wrote:
> Hello,
>
> I am trying to push a new version of my package to git.bioconductor.org. I
>
Hello,
I am trying to push a new version of my package to git.bioconductor.org. I
was able to do that in the past. But I've recently changed my public key
and not sure whether this causes a problem. However, I can see my new
public key here - https://github.com/wikiselev.keys - and it is the