161–170 of 298 posts
Earlier quoted context omitted.
It's also completely unloved. Even MSFT Azure's own documentation regularly treats it as a second class citizen to GitHub. I have no idea why they don't just deprecate the service and officially feature freeze it. Honestly that's the case with a lot of Azure services though.
It's the boards. GitHub issues doesn't let you do all the arcane nonsense Azure DevOps' boards let you do.
Can 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…
The ultimate irony is that Linus Thorvalds designed git with the Linux kernel codebase in mind to work without any form of infrastructure centralisation. No repo trumps any other. Surely some of your crazy kids can rummage up a CI pipeline on their laptop? 8) Anyway, I only use GH as something to sync interesting stuff from, so it doesn't get lost.
I’ve only worked on a team once where we all were set up as remotes to each other and that was over a decade ago.
The GitHub Status Page does not visualize these very well but you can see them parsed out and aggregated here:
Earlier 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…
Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete. It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to…
I don’t think GitHub cares about reliability if it does anything less than that.
I know people have other problems with Google, but they do actually have incredibly high uptime. This policy was frequently applied to entire orgs or divisions of the company if they had one outage too many.
Earlier quoted context omitted.
Yes, millions of people running code agents around the clock, where every tiny change generates a commit, a branch, a PR, and a CI run.
I simply do not believe that all of these people can and want to setup a CI. Some maybe, but even after the agent will recommend it only a fraction of people would actually do it. Why would they?
Earlier quoted context omitted.
Yes, millions of people running code agents around the clock, where every tiny change generates a commit, a branch, a PR, and a CI run.
I simply do not believe that all of these people can and want to setup a CI. Some maybe, but even after the agent will recommend it only a fraction of people would actually do it. Why would they?
All the while you're playing a wordle and reading the news on the morning commute.
It's actually a good workflow for silly throw away stuff.
Earlier quoted context omitted.
IME this all started after MSFT acquired GitHub but well before vibe coding took the world by storm. ETA: Tangentially, private repos became free under Microsoft ownership in 2019. If they hadn't done that, they could've extracted $4 per month from every vibe coder forever(!)
Is someone who is not really using github's free service losing something important?
Earlier quoted context omitted.
The ultimate irony is that Linus Thorvalds designed git with the Linux kernel codebase in mind to work without any form of infrastructure centralisation. No repo trumps any other. Surely some of your crazy kids can rummage up a CI pipeline on their laptop? 8) Anyway, I only use GH as something to sync interesting stuff from, so it doesn't get lost.
I wonder how many engineers have even worked on a git repo with multiple remotes. I’ve only worked on a team once where we all were set up as remotes to each other and that was over a decade ago.
Can 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…
The ultimate irony is that Linus Thorvalds designed git with the Linux kernel codebase in mind to work without any form of infrastructure centralisation. No repo trumps any other. Surely some of your crazy kids can rummage up a CI pipeline on their laptop? 8) Anyway, I only use GH as something to sync interesting stuff from, so it doesn't get lost.
https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco...
This (multiple major outages a day) has unfortunately been happening for quite a while now -- on the 2nd of February, 2026 for instance. The GitHub Status Page does not visualize these very well but you can see them parsed out and aggregated here: https://mrshu.github.io/github-statuses/