GitHub was having issues
githubstatus.com
GitHub was having issues
1–10 of 96 posts
Re: GitHub was having issues
#2Just found this out now, which is why I decided to submit my current blog post as it is :D But I'll finish it soon enough eheh
Re: GitHub was having issues
#3OT but why did it capitalize the title like that? I submitted "GitHub is having issues". I don't see that for other submissions (unless people manually edit them afterwards).
EDIT: Before the change to "GitHub was having issues" it had converted my original submission from "GitHub is having issues" to "GitHub Is Having Issues".
Re: GitHub was having issues
#4What's the reason these Git services have so many issues all the time?
Re: GitHub was having issues
#5Here we go again [0] and again [1] and again [2] and again [3].
Time to reset the counter once again. Now everything there is degraded performance. Oh dear.
Consider a self-hosted alternative or have one as a backup like I have said before.
[0] https://news.ycombinator.com/item?id=27192869
[1] https://news.ycombinator.com/item?id=27172443
Re: GitHub was having issues
#6For people using GitHub Actions how often do these types of incidents impact your CI/CD?
Re: GitHub was having issues
#7What's the reason these Git services have so many issues all the time?
possibly Azure?
Re: GitHub was having issues
#8Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253)
Re: GitHub was having issues
#9What's the reason these Git services have so many issues all the time?
possibly Azure?
Doesn't look like it, unless the status-page update is also affected :)
Re: GitHub was having issues
#10I would bet on it being related to their identity server. It seems to almost work in browser(s) where I was signed on - but in a new browser, it gives HTTP 500 after SSO.