Re:GitHub major issues - repos have "lost" commits and site ...
by andrewljohnson on Saturday January 29, 2011 @11:49PM
(#2157404)
This seems to be fixed now - for my repo at least.
The GitHub guy saying it was a "JavaScript display error" is incorrect though. I was pulling a repo and getting an old version.
EDIT: I'm not getting the javaScript display error, but I'm still missing my commit, so I guess these errors are unrelated :/
Re:GitHub major issues - repos have "lost" commits and site ...
by mojombo on Sunday January 30, 2011 @12:10AM
(#2157440)
Did you file a support ticket for this? It sounds like an unrelated problem. We can investigate if you let us know what repo is causing the problem. Visit http://support.github.com or email [email protected].
Re:GitHub major issues - repos have "lost" commits and site ...
by andrewljohnson on Sunday January 30, 2011 @12:16AM
(#2157449)
I posted the name of the repo to the thread, and someone else on the thread is confirming the same problem.
Re:GitHub major issues - repos have "lost" commits and site ...
by andrewljohnson on Monday January 31, 2011 @03:18PM
(#2162993)
It turns out that GitHub didn't lose any of my commits. All future readers should ignore my comments on this.
Re:GitHub major issues - repos have "lost" commits and site ...
by andrewljohnson on Monday January 31, 2011 @03:17PM
(#2162992)
This was my fault. GitHub was never messed up.
Re:GitHub major issues - repos have "lost" commits and site ...
by mfukar on Sunday January 30, 2011 @08:32AM
(#2158002)
For what it's worth, I was pulling & pushing just fine while the error was displayed on my repositories, but other people reported commits lost or mangled. Maybe there was something more to the Javascript display error?
"Sorry guys, there was a Javascript error displaying an error when there was none. We've deployed a fix for this and everything should be good to go."