search for: manipulatewidget

Lately I've been doing some work with the manipulateWidget package, which lives on Github at https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I found a bug, so being a good community member, I put together a patch. Since the package lives on Github, I followed instructions to put together a "pull request": - I forked th...

...rked state of the repo. Branches keepclass2 through to keepclass5 are my attempts to do that. As far as I can see they are all the same as keepclass, which was branched from the head of the master branch of my fork. > > Are the two commits here your fixes? > https://github.com/dmurdoch/manipulateWidget/commits/master Those are both part of the first PR. There's a third commit in keepclass (and the other branches too...) If you or someone else tells me the magic commands I need to do what I want, I'll appreciate it. But the main point of my post is that this is something that should...

When you create a branch for your bug fix, don't create it off the previous fix. Create it off the original, forked state of the repo. Are the two commits here your fixes? https://github.com/dmurdoch/manipulateWidget/commits/master Gabor On Wed, Jan 24, 2018 at 11:17 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > Lately I've been doing some work with the manipulateWidget package, which > lives on Github at > https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I...

...e reference; I already followed Gabor's more complicated instructions and have solved the immediate problem.) Duncan Murdoch > I?aki > > > > 2018-01-25 0:17 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: >> Lately I've been doing some work with the manipulateWidget package, which >> lives on Github at >> https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I >> found a bug, so being a good community member, I put together a patch. >> >> Since the package lives on Github, I followed instructions to put together a...

...nches keepclass2 through to keepclass5 are my attempts to do that. As far > as I can see they are all the same as keepclass, which was branched from the > head of the master branch of my fork. >> >> >> Are the two commits here your fixes? >> https://github.com/dmurdoch/manipulateWidget/commits/master > > > Those are both part of the first PR. There's a third commit in keepclass > (and the other branches too...) > > If you or someone else tells me the magic commands I need to do what I want, > I'll appreciate it. But the main point of my post is that...

...URL to use in 2) Github would not allow me to fork, because I already had a fork of the same repository. I suppose I could have set up a new user and done it. I don't know if cloning the original would have made a difference. I don't have permission to commit to the original, and the manipulateWidget maintainers wouldn't be able to see my private clone, so I don't see how I could create a PR that they could use. Once again, let me repeat: this should be an easy thing to do. So far I'm pretty convinced that it's actually impossible to do it on the Github website without hac...

...and I put my fix on top of the master branch, which complicates things a bit. But you can always rename your fork's master and pull it again from upstream. I?aki 2018-01-25 0:17 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: > Lately I've been doing some work with the manipulateWidget package, which > lives on Github at > https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I > found a bug, so being a good community member, I put together a patch. > > Since the package lives on Github, I followed instructions to put together a > "pull requ...

...to keepclass5 are my attempts to do that. As far >> as I can see they are all the same as keepclass, which was branched from the >> head of the master branch of my fork. >>> >>> >>> Are the two commits here your fixes? >>> https://github.com/dmurdoch/manipulateWidget/commits/master >> >> >> Those are both part of the first PR. There's a third commit in keepclass >> (and the other branches too...) >> >> If you or someone else tells me the magic commands I need to do what I want, >> I'll appreciate it. But the m...

...ndency ?arm? is not available for package ?mi? * removing ?/home/ernes/R/x86_64-pc-linux-gnu-library/3.5/mi? ERROR: dependency ?rio? is not available for package ?car? * removing ?/home/ernes/R/x86_64-pc-linux-gnu-library/3.5/car? ERROR: dependencies ?shiny?, ?miniUI? are not available for package ?manipulateWidget? * removing ?/home/ernes/R/x86_64-pc-linux-gnu-library/3.5/manipulateWidget? ERROR: dependency ?car? is not available for package ?RcmdrMisc? * removing ?/home/ernes/R/x86_64-pc-linux-gnu-library/3.5/RcmdrMisc? ERROR: dependency ?mi? is not available for package ?sem? * removing ?/home/ernes/R/x86_...

...> > Github would not allow me to fork, because I already had a fork of the same repository.? I suppose I could have set up a new user and done it. > > I don't know if cloning the original would have made a difference. I don't have permission to commit to the original, and the manipulateWidget maintainers > wouldn't be able to see my private clone, so I don't see how I could create a PR that they could use. > > Once again, let me repeat:? this should be an easy thing to do.? So far I'm pretty convinced that it's actually impossible to do it on the Github website...

...re Carpentry workshop. Happy to detail off-list, it adds less than 10 lines to ~/.bashrc. Dirk | | Duncan Murdoch | | > I?aki | > | > | > | > 2018-01-25 0:17 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: | >> Lately I've been doing some work with the manipulateWidget package, which | >> lives on Github at | >> https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I | >> found a bug, so being a good community member, I put together a patch. | >> | >> Since the package lives on Github, I followed instructions to put t...

...except that the "..." contains nothing, because I want this branch to continue. But now my problem is that I can't see any way to tell Github about this new branch. I ran git push origin upstreamMaster and got Total 0 (delta 0), reused 0 (delta 0) To https://github.com/dmurdoch/manipulateWidget * [new branch] upstreamMaster -> upstreamMaster but that branch doesn't show up in the Github web site. Any suggestions? Duncan Murdoch > > 4) open a fresh new PR from "patch2" (the first one is intact).

On 25/01/2018 7:44 AM, G?bor Cs?rdi wrote: > On Thu, Jan 25, 2018 at 12:34 PM, Duncan Murdoch > <murdoch.duncan at gmail.com> wrote: > [...] >> but that branch doesn't show up in the Github web site. > > It is right there: > https://github.com/dmurdoch/manipulateWidget/branches > >> Any suggestions? > > Personally I would suggest to call it master, because it is just > easier. Your master should correspond to the upstream master, and you > can do your own stuff in other branches. That makes sense, but I don't see a way to rename branch...

...;> >> On Thu, Jan 25, 2018 at 12:34 PM, Duncan Murdoch >> <murdoch.duncan at gmail.com> wrote: >> [...] >>> >>> but that branch doesn't show up in the Github web site. >> >> >> It is right there: >> https://github.com/dmurdoch/manipulateWidget/branches >> >>> Any suggestions? >> >> >> Personally I would suggest to call it master, because it is just >> easier. Your master should correspond to the upstream master, and you >> can do your own stuff in other branches. > > > That makes sens...

...because I want this > branch to continue. > > But now my problem is that I can't see any way to tell Github about this > new branch. I ran > > git push origin upstreamMaster > > and got > > Total 0 (delta 0), reused 0 (delta 0) > To https://github.com/dmurdoch/manipulateWidget > * [new branch] upstreamMaster -> upstreamMaster > > but that branch doesn't show up in the Github web site. > > Any suggestions? > > Duncan Murdoch > > >> 4) open a fresh new PR from "patch2" (the first one is intact). >> > > ___...