Incident with Webhooks (githubstatus.com)

Getting failed pushes, failed PR creation, failed CI pipelines.

Who else?

Can't merge PRs atm

Yeah there are some issues. PR is stuck at "Checking for the ability to merge automatically..."

By accident I landed on https://us.githubstatus.com/ and everything was green. At first, I thought, yeah sure, just report green, then I realized "GitHub Enterprise Cloud" in the title. There is also a EU mirror: https://eu.githubstatus.com

Edit:

The report just updated with the following interesting bit.

> We identified a faulty network component and have removed it from the infrastructure. Recovery has started and we expect full recovery shortly.

The thing that's been annoying me for a few weeks is an always-on notification, but my notification page shows no unread notifications.

I experienced an outage (website and any push, pull commands) that lasted for about 1-2 hours on Oct 7th but didn't see anything on their status page. There was definitively a spike on https://downdetector.ca/status/github/, so I know it wasn't just my ISP.

It’s kind of funny that the top two posts right now are:

    1. Why Self-Host?
    2. GitHub Issues

How long before moderately sized companies start hosting their own git servers again. Surely it wouldn’t be that difficult unless your repos are absolutely massive. GitHub outages are so common these days

I wish the most popular software forge didn't include a bunch of other software solutions like issue tracking or forums.

Having everything in one service definitely increases interoperability between those solutions, but it definitely decreases stability. In addition, each of the other systems is not the best in their class (I really detest GH Actions for example).

Why do so many solutions grow so big? Is it done to increase enterprise adoption?

Oh it's that time of the week again.

I stopped using Actions for side projects a few months ago, things are simpler now (I run tests locally).

I felt like Actions were a time sink that trick you into feeling productive - like you're pursuing 'best practice' - while stealing time that could otherwise be spent talking to users or working on your application.

For anyone who wants context, here is the entire history of github "Issues"

https://www.githubstatus.com/history

seems like Microsoft can't keep this thing from crashing at least three times a month. At this rate it would probably be cheaper just to buy out Gitlab.

Wondering when M$ will cut their losses and bail.

I'm not looking forward to the Azure migration and potential for more issues in the coming year

To run your github actions locally, we've had decent success with this tool: https://github.com/nektos/act

Just be warned if you try it out that if you don't specify which workflow to run, it will just run them all!