3 ms·

Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.

• vincentkriek 4y ago
  Same here! Was going crazy what I was doing wrong. Renamed my branch to see if that was causing anything.
  • themanmaran 4y ago
    Small world. I assumed I had created a duplicate branch name or something, and renamed the branch as well before hitting up google.
• activitypea 4y ago
  For me it went down just as I was logging in, I thought I was banned or something :')
  • Avicebron 4y ago
    Same, I thought they had finally come for me because I refuse to change master to main.
• czx4f4bd 4y ago
  Same here haha. StackOverflow informed me that it means GitHub is down, and indeed it was. I have to wonder if Git could somehow report this better. I guess it depends on exactly how GitHub is down, but "fatal error in commit_refs" made me worry that my local repo was somehow hosed.
  • TheSoftwareGuy 4y ago
    I think it can? whenever I can't connect to my company's git server I get a `failed to connect to git.company.com` message. or something like that
  • masklinn 4y ago
    It reports what it has, if it manages to connect but fetching the metadata or whatever fails, that’s what it’s going to report. If it can’t even connect it’ll tell you that, but I would assume on github the client will always manage to connect unless their entire network is down.
• arcosdev 4y ago
  I was rebasing and thought I had committed some kind of git sin that I wasn't aware of.