If you listen closely you can hear the sound of all bower-dependent builds on earth failing in synchrony

why only bower-dependent?

I'm guessing the parent doesn't mean only bower, but bower uses github as the source of packages/code (I don't use bower, so I'm only going from memory). On a build that downloads everything 'fresh' it's not going to be able to get sources that are only on github.

Bower certainly isn't the only thing that does it. It's a trend that's becoming more and more common.

I was in a go tutorial a couple of years ago where the presenter was including directly from github.

And sitting in a ruby talk when the rubygems compromise happened just after everyone had been told to go upgrade a gem because of flaws in a specific gem.

It's not unique, but it is terrible.

Unlike most other package managers, bower doesn't actually host packages. It just finds that at Git URLs, which are almost invariably on GitHub.

As GitHub queues up webhooks, we're bracing for impact at buddybuild! :)

You shouldn't notice a webhook deluge because the site isn't generating events. I'm watching our webhook services though and will let you know if that changes.

Hi Kyle!

It looks like webhooks are wedged.. no?

Everything should be A-OK now. If not, hit up github.com/contact :)

But no one can do anything to generate new webhooks.

pushes have been working for the past 10-15 minutes... pulls for 5-10 minutes.

Which is, in a sense, a bit disturbing.

Yup, a coworker was wondering why a build failed, a minute later I saw this.

Well, it's not like we have invented binary and source packages two decades ago, so people don't need to re-download and re-build their build-time dependencies every time they start compilation.

Oh wait, we have.

Yep, but nobody ever includes them. Nice stuff to automate, gotta chek if there is already DevOpsy stuff to fix that, and if there isn't, got me a new weekend project...

It is obviously gonna be hosted on GitHub. Oh, the irony...