Related to the Twitter source code leak, perchance?
GitHub issue - resolved
31–40 of 169 posts
Re: GitHub issue - resolved
#32Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.
For me it went down just as I was logging in, I thought I was banned or something :')
Same, I thought they had finally come for me because I refuse to change master to main.
Re: GitHub issue - resolved
#33Earlier quoted context omitted.
I like to reduce the single point of failure count in my projects as much as I can, with common sense. My backup system is running a few cli commands instead of git push, so it's a no brainer. YMMV.
How sure are you that none of those commands has a dependency on GitHub infrastructure?
Because I use Github only for git hosting and actions (building & deploying containers). In this case, code is already in my computer, and I can build and ssh to server and pull&run the new container.
"docker buildx build ... -push" "ssh ...@..." "docker pull ..." "docker compose up ..."
Re: GitHub issue - resolved
#34Because this needs to happen as one prepares to push to day's last deploy. Back to backups. Have backups for critical systems, people. In my case, it's building docker containers locally and luckily deploying to one server via ssh.
Depends on the context. I need to push to a repo and QA needs to test the app, but since I can't push, they can't. No other practical way (other than setting up another origin on Bitbucket or GitLab, or emailing/zipping sending etc).
Yea, heavily depends on the context. In my case, it's a single dev deploying to single server, so no biggie.
Re: GitHub issue - resolved
#35https://www.githubstatus.com/incidents/52z0j6phhnjs
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc.
However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
Re: GitHub issue - resolved
#36Ever since Microsoft took over...
...Github has gotten significantly better.
Re: GitHub issue - resolved
#37Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.
Same here! Was going crazy what I was doing wrong. Renamed my branch to see if that was causing anything.
Small world. I assumed I had created a duplicate branch name or something, and renamed the branch as well before hitting up google.
Re: GitHub issue - resolved
#38Related to the Twitter source code leak, perchance?
Given that looking at repos is just about the only thing that I can do then I'd say that seems unlikely.
Re: GitHub issue - resolved
#39Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.
Re: GitHub issue - resolved
#40[dead]