[Rd] R-Forge > GitHub?
otoomet @end|ng |rom gm@||@com
Sat Jun 29 05:25:35 CEST 2019
Apparently your username/password are wrong. Can you clone/push from other
You do not need authorization when cloning a public repo, so even incorrect
credentials may work (haven't tested this though). But for push you have
to have that in order.
I suggest you create ssh keys, upload those to GH, and use ssh
authorization instead of https.
On Fri, Jun 28, 2019 at 8:18 PM Spencer Graves <spencer.graves using prodsyse.com>
> Thanks to Duncan, Henrik and Henrik, Brian, and Gábor:
> I created a local copy of the new GitHub version using the
> git clone https://sbgraves237:firstname.lastname@example.org/sbgraves237/Ecdat.git
> That worked in the sense that I got a local copy. However, after
> I rolled the version number and did "git commit" on the DESCRIPTION
> files, my "git push" command generated the following:
> remote: Invalid username or password.
> fatal: Authentication failed for
> What am I missing? [Note: I used my actual GitHub password in
> place of "mypassword" here, and this "Authentication failed" message
> reported the GitHub password I used here.]
> p.s. I'm doing this under macOS Mojave 10.14.5. Also, I added
> ".onAttach" functions to the R-Forge versions as Brian G. Peterson
> suggested. That seemed to work fine.
> On 2019-06-28 07:13, Duncan Murdoch wrote:
> > On 28/06/2019 6:26 a.m., Gábor Csárdi wrote:
> >> Instead, you can do as Duncan suggested, and put a README in your
> >> R-Forge
> >> repository, that points to *your* GitHub repositor(y/ies). Then the
> >> https://github.com/rforge/ecdat read only mirror will pick this up
> >> and will
> >> point there as well.
> > Just for the record: that was Henrik Singmann's suggestion, I just
> > agreed with it.
> > Duncan Murdoch
> [[alternative HTML version deleted]]
> R-devel using r-project.org mailing list
[[alternative HTML version deleted]]
More information about the R-devel