Re:GitHub user sends notification to 400k users
by fellellor on Sunday June 05, 2022 @02:23AM
(#31628515)
Sometimes fixing a typo would be a new coder’s first open source commit. It’s pretty stupid to assume every new PR would be a major new feature or bug fix. It makes OSS unnecessarily hostile to get into.
Although this commit in question isn’t even that sadly.
Re:GitHub user sends notification to 400k users
by ushakov on Saturday June 04, 2022 @11:03PM
(#31627615)
probably for resume?
“Contributed quality improvements to Epic Games Unreal Engine”
luckily, GitHub makes it terribly easy to verify how much and what you actually contributed
Re:GitHub user sends notification to 400k users
by wonderbore on Saturday June 04, 2022 @11:38PM
(#31627787)
The problem here is that they’re not even trying. How can they not know that such PR would never be merged? For this reason I don’t think public contributions are why they send the PRs
Re:GitHub user sends notification to 400k users
by ushakov on Saturday June 04, 2022 @11:49PM
(#31627832)
that might be obvious to me and you, but i don’t think the author knew
Re:GitHub user sends notification to 400k users
by spatulon on Sunday June 05, 2022 @07:02AM
(#31629845)
The main repo I work on for my job is open-source, and yes, it happens fairly regularly that someone opens a nonsensical PR that might randomly perturb some Markdown or YAML file, or attempt to merge commits from some other developer's in-progress branch.
I'd say we only get them about once every week or so, but then the repo is not anywhere near as high-profile as the Unreal Engine, nor as likely to be on the radar of children.
[1] https://www.theregister.com/2020/10/01/digitalocean_hacktobe...