Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub is investigating an incident with Pull Requests, Issues and Webhooks

githubstatus.com

Post reply on HN
Print view View original

31–40 of 61 posts

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#31

Post by johnfn »

midasuni wrote: post #25
selykg wrote: post #13

Earlier quoted context omitted.

Before Microsoft bought them they were basically at a standstill and no new features were being added to the product. At least, that's my recollection of it, perhaps someone can correct me if I'm wrong.

My screwdriver doesn’t seem to need more features. It’s nice stable and reliable.

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 EXTREMELY long time to ship emoji reactions, which struck me as a fairly trivial feature. I stand by the point that GH ships features faster post-acquisition, though.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#33

Post by FridgeSeal »

JLCarveth wrote: post #9

GitHub outages seem to have happened a lot this year.

I’ve also noticed a lot of consistency issues on their site recently.

Open PR; someone comments-doesn’t show up no matter how many hard refreshes, browser restarts, etc. Push a commit to your branch - doesn’t show up in the PR, but shows up in the commit history. If you have auto-merge ticked, it might never merge even when it meets the conditions, and if the branch merges you won’t know, because again, the PR never updates and it still looks open.

I have these issues- in varying degrees of duration and severity- about once a week.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#34

Post by brazzledazzle »

calvinmorrison wrote: post #11

Web hooks are not reliable. When engineering your system, you need to implement a scheduled based watcher to go back and clean up hook issues.

Yeah GitHub doesn't like when you do frequent polling over hooks but you pretty much need to have something polling (infrequently) to catch undelivered hooks.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#35

Post by hn_ta456 »

gherkinnn wrote: post #28
unicornmama wrote: post #22

Frustrating and unproductive day for those trapped in CI driven development mode. Mild annoyance for the rest of us.

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.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#36

Post by travoc »

midasuni wrote: post #25
selykg wrote: post #13

Earlier quoted context omitted.

Before Microsoft bought them they were basically at a standstill and no new features were being added to the product. At least, that's my recollection of it, perhaps someone can correct me if I'm wrong.

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.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#37

Post by Springtime »

johnfn wrote: post #31
midasuni wrote: post #25

Earlier quoted context omitted.

My screwdriver doesn’t seem to need more features. It’s nice stable and reliable.

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...

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#39

Post by ad404b8a372f2b9 »

johnfn wrote: post #31
midasuni wrote: post #25

Earlier quoted context omitted.

My screwdriver doesn’t seem to need more features. It’s nice stable and reliable.

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…

That's not true. Reactions on comments were implemented long before the acquisition. And people still did +1.

On the other hand, what they didn't have was search locked behind a login screen.

Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks

#40

Post by stabbles »

johnfn wrote: post #31
midasuni wrote: post #25

Earlier quoted context omitted.

My screwdriver doesn’t seem to need more features. It’s nice stable and reliable.

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 better or worse.

Post reply on HN