Confusingly I’m getting the following error here:
$ git reset --hard '28032eaf38530b96c92aef3df42841aa8613a2f6'
fatal: Could not parse object '28032eaf38530b96c92aef3df42841aa8613a2f6'.
I believe that’s the right hash that’s running on my production server, and it looks to exist on github: Commits · discourse/discourse · GitHub
Looks clean otherwise:
$ git status
# On branch master
nothing to commit, working directory clean
$ git fsck
Checking object directories: 100% (256/256), done.
Checking objects: 100% (5038/5038), done.
I’m wanting to stage the upgrade to 2.7.0.beta2, but this looks to be preventing me from starting at the same point as the production servers ![]()