Earlier quoted context omitted.
or forgejo!
Yeah man. Forgejo (albeit it being a weird name from a language that nobody wants to use), is doing very well in my homelab. When I worked at the univerity we used Gitea. Every job outside of univerity I had used Gitlab self hosted. While I don't like the UI or any aspect of Gitlab a lot, it gets the job done.
Another GitHub outage in the same day
31–40 of 298 posts
Re: Another GitHub outage in the same day
#32It's just "yet another day of business as usual" as this point.
Re: Another GitHub outage in the same day
#33I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works . Any good recommendations?
Re: Another GitHub outage in the same day
#34Re: Another GitHub outage in the same day
#35Earlier quoted context omitted.
I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…
The trend of "non-functional software" is happening everywhere. See the recent articles about Copilot in Notepad, failing to start because you aren't signed in with your Microsoft Account. We are in a future that nobody wanted.
Nor deserved.
Re: Another GitHub outage in the same day
#36Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…
As an aside, God, Azure DevOps, what a total pile of crap that product is My "favourite" restriction that an Azure DevOps PR description is limited to a pathetic 4000 characters.
Re: Another GitHub outage in the same day
#37Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…
I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…
Re: Another GitHub outage in the same day
#38Re: Another GitHub outage in the same day
#39Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…
As an aside, God, Azure DevOps, what a total pile of crap that product is My "favourite" restriction that an Azure DevOps PR description is limited to a pathetic 4000 characters.
Re: Another GitHub outage in the same day
#40Earlier quoted context omitted.
I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…
We loved Github as a product when it needed to return or profit beyond "getting more users". I feel this is just the natural trajectory for any VC-funded "service" that isn't actually profitable at the time you adopt it. Of course it's going to change for the worse to become profitable.