Hello,
thanks Nitesh. I reverted the commits accordingly.
Cheers,
Simon
On 10.09.19 16:45, Turaga, Nitesh wrote:
Hi Simon,
I take this back actually. I think the best way forward is just undo the code
changes, and add a new version number to it ( 1.9.3) and push.
Step 1,
Since y
Hi Simon,
I take this back actually. I think the best way forward is just undo the code
changes, and add a new version number to it ( 1.9.3) and push.
Step 1,
Since your version 1.9.2 is already on Bioconductor, first sync your
GitHub with that version.
Step 2,
Undo the code
Hi Simon,
Bioconductor's git system doesn't allow force push (This is a feature) . It
only allows a force push by administrators (Bioconductor Core team). Please
send me a link to your GitHub repo which is at 1.9.0, and I will sync it for
you.
I've updated the link where the instructions are
Hi,
this is the way described in [1].
Cheers,
S
On 10.09.19 13:51, Neumann, Steffen wrote:
Hi,
that's not the git way to do it. Your previous commit is already
out in the open, if you git reset, that would be dangling in the air.
I really love this decision tree:
https://sethrobertson.githu
Hi,
that's not the git way to do it. Your previous commit is already
out in the open, if you git reset, that would be dangling in the air.
I really love this decision tree:
https://sethrobertson.github.io/GitFixUm/fixup.html
which in your case will get you probably to
https://sethrobertson.gi
