+ [2020-04-27T23:47:31Z] __Myst__ what's the right way to pass secrets to a command which only takes them from the CLI in a github action?
+ [2020-04-28T21:10:02Z] vadique hola here, I have a problem
+ [2020-04-28T21:10:38Z] vadique I did git rebase and then git push -f, but I have a patch which is to be applied upon that old variant of commit
+ [2020-04-28T21:10:56Z] vadique is there any chance to recover that version, before git push -f ?
+ [2020-04-28T21:38:47Z] vadique git am -3 helped me

message no. 179890

Posted by vadique in #github at 2020-04-28T21:10:38Z

I did git rebase and then git push -f, but I have a patch which is to be applied upon that old variant of commit
+ [2020-04-29T00:03:03Z] Viking667 I'm noticing a strange problem. I forked a project, they've updated from 7.1.10-xx-gxyzabcdef to 7.2.0-xx-gxyzabcdef, yet even though I've done "git pull upstream master" my tags didn't change to match upstream.
+ [2020-04-29T00:03:34Z] Viking667 repos involved are "upstream" is dolphinsmalltalk/Dolphin, mine is brickviking/Dolphin
+ [2020-04-29T00:06:12Z] Viking667 I recently synchronised (today), my "git describe --tags" says v7.1.10-52-g173fe847, theirs is v7.2.0-2-g173fe847
+ [2020-04-29T00:22:46Z] Viking667 I'm not sure whether the problem I have is strictly a github problem, or more properly a git problem.
+ [2020-04-29T00:33:36Z] R2robot doubt it's anything to do with github itself