101–110 of 132 posts
This is bigger than github: https://downdetector.com
Looks like Azure might be the common denominator.
Can't wait for Microsoft to go the IBM way.
Yeah I think I've finally had enough. I need to start seriously advocating for alternatives since this is starting to impact our business. It's clearly not getting any better.
If you want a GitHub-like UI (with org/repo structure limitations) use either Forgejo or Gitea. If you want a similar but different experience use GitLab. If you want something more akin to the kernel experience (i.e. hosting, flexible repository structure, user auth via ssh keys, and a simple web UI) use gitolite with cgit, or alternatively gitweb.
Hate GitHub being down, plus hate AI stealing your code? Join sourcehut--it has worked great for me, and I'd love to see it flourish as a platform.
- IT policies around GH accounts make no sense. It's a long story but, in short, you can't use any of your pre-existing GH accounts whether personal or professional (as in, an account I made exclusively for $DAYJOB before The Synergy Mandate) and must create a new one aligned with IT conventions.
- We don't monorepo hence we made extensive use of groups. There is no direct mapping for this concept in GitHub so we have to manually namespace projects.
- And now of course GH's no-nines availability :(
For my team, profit happens to be sensitive to our release dates---a day or two of delay can really make the difference if we'll make the month's projections or not. In another world, I would proactively mirror our profit-essential code but it's not worth the risk making a skunkworks guerilla effort. I'd like to think we can blame The Synergy Mandate in a few postmortems in the near future but of course I did not graduate yesterday, I know that's not gonna happen.
Thoughts and prayers we keep hitting our profit projections and they don't axe our product for underperformance.
(Writing this down, I can really feel how this job has changed since I joined.)
We're barely starting to see AI's impact on infra - probably (FWIW https://diversion.dev is at 100% uptime. Different scale, obviously, but also we're not Microsoft.)
I suggest testing your website with uBlock (and all its filter lists enabled). All I see is an almost empty page. Don't point to JS or CSS on third-party CDNs because due to the changes in cross-site sharing, neither Chrome nor Firefox will benefit from cacheing.
Earlier quoted context omitted.
Or last week's "If you use merge queue, oopsie, we accidentally destroyed your trunk", which also failed silently.
I was surprised that incident didn’t seem to get as much attention since that was a pretty major data corruption bug, but I guess it was a much smaller scope of impacted repos/customers than a lot of these availability issues?
Earlier quoted context omitted.
Or last week's "If you use merge queue, oopsie, we accidentally destroyed your trunk", which also failed silently.
I was surprised that incident didn’t seem to get as much attention since that was a pretty major data corruption bug, but I guess it was a much smaller scope of impacted repos/customers than a lot of these availability issues?
It's easier, and somehow more reliable to self-host a Gitea instance on consumer hardware than it is to rely on GitHub.