Live data from Hacker News

GitHub Merge Queue Silently Reverted Code

githubstatus.com

41–50 of 52 posts

Re: GitHub Merge Queue Silently Reverted Code

#41
post #29
post #28

Earlier quoted context omitted.

That's the American style, and it's stupid.

It's English, my fair cross-dressing sweaty nerd. Go read a book for once in your lifetime. Harry Potter at the very least. “The best,” replied Severus Snape. -- Harry Potter And The Deathly Hallows, p.1

You clearly have no idea what you're talking about.

Re: GitHub Merge Queue Silently Reverted Code

#42
post #24

Earlier quoted context omitted.

I don't care to associate with people who are offended by being corrected. They can sod off. And I never go to what you Americans call "parties".

> And I never go to what you Americans call "parties". Whenever you use quotes and they are directly followed by punctuation you must include the punctuation within the quotes. "parties."

Literally just watched the video of you posting this. Amazing how few people got the irony.

Re: GitHub Merge Queue Silently Reverted Code

#43
post #30

Earlier quoted context omitted.

Yes it does. The original commenter can learn how to spell better which makes clear communication easier, and don't forget that other people read internet discussions and they may be learning new words or realizing they also didn't know how to spell a word correctly. You seem offended at the prospect of people learning how to do something correctly, I don't get it.

MarkMarine, the person you responded to, is the original commenter. I agree with your point but clearly MarkMarine has no interest in learning how to communicate well.

I actually missed that, that makes the whole thing even funnier. Reacting this way to being corrected is almost as embarrassing as GitHub breaking merges :p

Re: GitHub Merge Queue Silently Reverted Code

#44

How did a bug like this get past their testing?

CoPilot broke github actions in such a way that if too many requests to start a workflow came in at the same time it would reduce the capacity of the build server's queue until you did a full manual reboot of the build server and completely reset the queue.

Some people are saying they aren't doing testing, I know this to be incorrect in one very important way. When it comes to people, the ways in which a co-worker is going to be wrong are predictable. When it comes to AI written code, there is zero predictability as to what could be wrong.

Trying to test AI written code is like writing code with no try catch blocks, and expecting the application to not crash within 15 minutes of giving to the end user. They will try everything you didn't think to explicitly handle, and when it comes to AI there is no try catch block for subtly incorrect or incomplete logic.

Re: GitHub Merge Queue Silently Reverted Code

#45
Checked all my PRs that merged on the 23:d. Checked out each branch locally, rebased on trunk and ran 'git diff'. One of them had a diff which was the entire change that was marked as merged in the GH web ui.

This happened in complete silence and since the PR in question was just code refactor I would most likely never have noticed.

Re: GitHub Merge Queue Silently Reverted Code

#46

Checked all my PRs that merged on the 23:d. Checked out each branch locally, rebased on trunk and ran 'git diff'. One of them had a diff which was the entire change that was marked as merged in the GH web ui. This happened in complete silence and since the PR in question was just code refactor I would most likely never have noticed.

Considering switching to original method of simple git repo hosting and email patches like the kernel does it. A workflow I favor. Turns out there are no hosting services which provide such solutions. Lots of manual hosting setup and config required... Sad that GitHub sort of cast the mold for how git hosting has been done for the past 2 decades.

Re: GitHub Merge Queue Silently Reverted Code

#47

Checked all my PRs that merged on the 23:d. Checked out each branch locally, rebased on trunk and ran 'git diff'. One of them had a diff which was the entire change that was marked as merged in the GH web ui. This happened in complete silence and since the PR in question was just code refactor I would most likely never have noticed.

Considering switching to original method of simple git repo hosting and email patches like the kernel does it. A workflow I favor. Turns out there are no hosting services which provide such solutions. Lots of manual hosting setup and config required... Sad that GitHub sort of cast the mold for how git hosting has been done for the past 2 decades.

[dead]

Re: GitHub Merge Queue Silently Reverted Code

#49

Earlier quoted context omitted.

> And I never go to what you Americans call "parties". Whenever you use quotes and they are directly followed by punctuation you must include the punctuation within the quotes. "parties."

Literally just watched the video of you posting this. Amazing how few people got the irony.

[deleted]

Re: GitHub Merge Queue Silently Reverted Code

#50

Earlier quoted context omitted.

> And I never go to what you Americans call "parties". Whenever you use quotes and they are directly followed by punctuation you must include the punctuation within the quotes. "parties."

Literally just watched the video of you posting this. Amazing how few people got the irony.

The comments on that video are wonderful. It's so heart-warming to see people laugh at Americans' "standards".
Post reply on HN