Frustrating and unproductive day for those trapped in CI driven development mode. Mild annoyance for the rest of us.
are github runners stalling?
GitHub is investigating an incident with Pull Requests, Issues and Webhooks
41–50 of 61 posts
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#42It'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
That tag line isn't for you. It's for aging C-suite exec's who like fancy sounding words.
As for not going down. Meh, at least you don't have to do on-call for it. That's kind of half the point of paying for SaaS. At the end of the day, it's just a human system.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#43It'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
Every week? You're being very generous to them
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#44Earlier quoted context omitted.
Before the MS acquisition, Github didn't even have emoji reactions on comments in issue threads, so people just spammed +1s if they had the same issue. It was terrible. (You can still see evidence of this on older repos.) They also didn't have like 5 billion other features that we now take for granted. EDIT: Sorry, this is incorrect. GH did ship them prior to the MS acquisition. I do however remember them taking an E…
They had reactions two years prior as confirmed by their blog post[1] about it. [1] https://github.blog/2016-03-10-add-reactions-to-pull-request...
Dang, you're right. Sorry about that.
I remembered that reactions irked me for some reason, but I had incorrectly tied it to the MS acquisition. The real issue was this: it took Github an extremely long amount of time to add a feature as simple as reactions. Github was founded in '08, and didn't add reactions for another eight years! But I distinctly remember once MS acquired them, they started shipping features left and right, and features much larger than simple emoji reactions.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#45It'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
They should understand this. If users move away who’s code will the rinse and resell?
Move where exactly? Bitbucket and GitLab aren't that great either.
I'm affected by GitHub outages maybe once every 2 months for a couple of hours. Sure, various parts go down but it's never something super impactful to my workflow.
It's not great but, IMHO, not outrage worthy.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#46Earlier quoted context omitted.
Before the MS acquisition, Github didn't even have emoji reactions on comments in issue threads, so people just spammed +1s if they had the same issue. It was terrible. (You can still see evidence of this on older repos.) They also didn't have like 5 billion other features that we now take for granted. EDIT: Sorry, this is incorrect. GH did ship them prior to the MS acquisition. I do however remember them taking an E…
Before this gets downvoted, are there any notable features that could only have been added thanks to the Microsoft acquisition? I think GitHub actions are pretty successful, which may not have been developed by Microsoft as it was launched right after acquisition, but I guess it's easier to keep free since it runs on their own hardware. I don't immediately see copilot as a GitHub feature, but maybe that'll change for…
I think you're asking a slightly incorrect question. Very few features could "only" be added thanks to the MS acquisition. What you really want to know is how many more features were added, thanks to MS. Or, how much longer would those features have taken to be built if GitHub was not acquired by MS. My gut feeling, seeing GH pre- and post-acquisition, says that a lot of the stuff they shipped post-MS would simply never have been shipped before.
Under MS, they shipped - just off the top of my head:
* dev containers
* vscode-github-in-the-browser
* github actions
* that extremely useful fuzzy-find that repos have (press t in any repo)
* copilot
I seriously doubt they could have shipped a single one of those things pre-MS.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#47Earlier quoted context omitted.
Before the MS acquisition, Github didn't even have emoji reactions on comments in issue threads, so people just spammed +1s if they had the same issue. It was terrible. (You can still see evidence of this on older repos.) They also didn't have like 5 billion other features that we now take for granted. EDIT: Sorry, this is incorrect. GH did ship them prior to the MS acquisition. I do however remember them taking an E…
Before this gets downvoted, are there any notable features that could only have been added thanks to the Microsoft acquisition? I think GitHub actions are pretty successful, which may not have been developed by Microsoft as it was launched right after acquisition, but I guess it's easier to keep free since it runs on their own hardware. I don't immediately see copilot as a GitHub feature, but maybe that'll change for…
GitHub Actions seems to use Azure a lot under the hood; given that they seemed to use AWS for older features (attachments, releases, etc.) it seems likely that it actually needed Microsoft.
My best guess, with no knowledge of what actually happened, is that it was derived from Azure Pipelines.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#48Earlier quoted context omitted.
My screwdriver doesn’t seem to need more features. It’s nice stable and reliable.
Modern impact drivers are pretty amazing if you have more than one screw to operate.
Yeah I don’t remember the last time I used a screw driver. Electric screw driver for tiny stuff (one of my fav tools of the last decade+) and a small impact driver for bigger screws.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#49Earlier quoted context omitted.
I have never worked, or know someone who has, at a place that doesn't rely on CI (does that make it CIDD?). Of all the *DDs, this is one of the few that is done without much complaint or major problems or controversies around it.
CI does make sense if your job entails endlessly churning web app features and UI.
That it be and applies to me. And countless others. Oh the drudge.
I also know countless people who work outside of CRUD world who rely on CI. The only exception I can think of are scientists who, well, tend not to use version control beyond folder naming. Not that I blame them, on the contrary.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#50Earlier quoted context omitted.
Before this gets downvoted, are there any notable features that could only have been added thanks to the Microsoft acquisition? I think GitHub actions are pretty successful, which may not have been developed by Microsoft as it was launched right after acquisition, but I guess it's easier to keep free since it runs on their own hardware. I don't immediately see copilot as a GitHub feature, but maybe that'll change for…
I think you're asking a slightly incorrect question. Very few features could "only" be added thanks to the MS acquisition. What you really want to know is how many more features were added, thanks to MS. Or, how much longer would those features have taken to be built if GitHub was not acquired by MS. My gut feeling, seeing GH pre- and post-acquisition, says that a lot of the stuff they shipped post-MS would simply ne…
> * that extremely useful fuzzy-find that repos have (press t in any repo)
I didn't know this. Thanks for the tip!