4 ms·
Just posted to the support page. "Sorry guys, there was a Javascript error displaying an error when there was none. We've deployed a fix for this and everythin
by wizard_2 16y ago
Just posted to the support page.
"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."
- andrewljohnson 16y agoThis 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 :/
- mojombo 16y agoDid 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 http://support.github.com or email support@github.com.
- andrewljohnson 16y agoI posted the name of the repo to the thread, and someone else on the thread is confirming the same problem.
- andrewljohnson 16y agoIt turns out that GitHub didn't lose any of my commits. All future readers should ignore my comments on this.
- andrewljohnson 16y agoThis was my fault. GitHub was never messed up.
- mfukar 16y agoFor 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?