Incident with Git Operations, Issues and Pull Requests [resolved]

  • Honest question, are any Hubers here able to shed some light on how GitHub has evolved since the Microsoft acquisition?

    I remember seeing tweets that suggested that a lot of the people from the Azure DevOps organisation have been moved to GitHub, whilst a lot of former GitHub employees have been sacked or left and that things like GitHub Actions have been migrated to .NET. Is there any truth to this?

    Also is GitHub being slowly pushed to use Azure as the underlying infrastructure?

    A lot of people say that outages have increased since the takeover and others say they have become less. I don't know but it certainly feels like a lot recently.

  • How stupid are we all to rely so heavily on this single point of failure which is so unstable?

    I cannot count the times it's been down or had temporary instability. It's easy to draw the conclusion that it happened after MS took over, but I honestly no longer remember how it was before.

  • Pull request eventually succeeded. Just "retry until the load balancer gives you a good node"

  • Earlier in the day GitHub actions went down as soon as I had pushed some changes and wanted a deployment to run. Talk about bad timing.

    It's a bit strange seeing GitHub having problems again in such short time. But to be fair, GitHub's scale is insanely huge. I'm surprised they can keep everything running fine 99% of the time.

  • Use git-bug. It never goes down, is about as private as possible, and the issue tracker UI is actually really pleasant. https://github.com/MichaelMure/git-bug

  • We picked Bitbucket instead of Github many years ago, basically because the person setting up the repos already knew Jira

    I’ve been very happy about that past decision lately, Bitbucket is just…boring. It works, rarely gets in the way, and the company doesn’t really partake in politics in the tech scene

  • Based on their status page it seems to affect only issues and pull requests … for now.

  • Noticed as well. It is up again now (Netherlands).

    Edit: Oops. Not up. Repo's aren't shown (error 500) sometimes. Refresh helps (maybe due to choice of load balancer as other comments refer to).

  • First day back from a break and GitHub is down, classic.

  • How much of GitHub stack is still Ruby? Is it an appropriate language at this scale?

  • Now the incident page states that the Git Operations are degraded as well.

  • Repo view just came back in this moment. Let's see how that evolves.

  • Man, they ought to put CoPilot in charge of their ops

  • All green lights now. :)

  • gh cli interface still works fine