#pull-requests — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pull-requests, aggregated by home.social.
-
From the Visual Studio blog...
In case you missed it earlier...
Review pull requests without leaving Visual Studio
https://devblogs.microsoft.com/visualstudio/review-pull-requests-without-leaving-visual-studio/ #Git #Productivity #VisualStudio #GitIntegration #PullRequests -
From the Visual Studio blog...
In case you missed it earlier...
Review pull requests without leaving Visual Studio
https://devblogs.microsoft.com/visualstudio/review-pull-requests-without-leaving-visual-studio/ #Git #Productivity #VisualStudio #GitIntegration #PullRequests -
From the Visual Studio blog...
Review pull requests without leaving Visual Studio
https://devblogs.microsoft.com/visualstudio/review-pull-requests-without-leaving-visual-studio/ #Git #Productivity #VisualStudio #GitIntegration #PullRequests -
From the Visual Studio blog...
Review pull requests without leaving Visual Studio
https://devblogs.microsoft.com/visualstudio/review-pull-requests-without-leaving-visual-studio/ #Git #Productivity #VisualStudio #GitIntegration #PullRequests -
🚨 Breaking news! #GitHub experiences the most thrilling of all tech catastrophes: a status page incident! 📉 Because nothing screams "exciting tech content" like subscribing to updates on pull requests and API requests gone awry. 🙄
https://www.githubstatus.com/incidents/xy1tt3hs572m #Incident #TechNews #StatusPage #APIUpdates #PullRequests #HackerNews #ngated -
🚨 Breaking news! #GitHub experiences the most thrilling of all tech catastrophes: a status page incident! 📉 Because nothing screams "exciting tech content" like subscribing to updates on pull requests and API requests gone awry. 🙄
https://www.githubstatus.com/incidents/xy1tt3hs572m #Incident #TechNews #StatusPage #APIUpdates #PullRequests #HackerNews #ngated -
Incident with Pull Requests, Issues, Git Operations and API Requests
https://www.githubstatus.com/incidents/xy1tt3hs572m
#HackerNews #GitHubIssues #GitOperations #APIRequests #PullRequests #TechIncident
-
Incident with Pull Requests, Issues, Git Operations and API Requests
https://www.githubstatus.com/incidents/xy1tt3hs572m
#HackerNews #GitHubIssues #GitOperations #APIRequests #PullRequests #TechIncident
-
Automatically getting API difference diagrams in your .NET PRs | by Morten Nielsen
https://xaml.dev/post/automatically-getting-api-difference-diagrams-in-your-net-prs
-
Automatically getting API difference diagrams in your .NET PRs | by Morten Nielsen
https://xaml.dev/post/automatically-getting-api-difference-diagrams-in-your-net-prs
-
Getting a bit sick of fielding LLM PRs. I understand why many projects have a no-LLM policy. I'm generally fine getting good PRs, LLM-aided or not, but the poor ones are just complete wastes of time. They all read the same, good or not, so I have to spend quite a bit of time sussing through it to determine which ones are useless or not. They're all "bug fixes" or "security improvements".
No, it does not make sense for an CLI argument parsing library to scan through argv to make sure it doesn't contain null pointers. That's ridiculous. No, it does not make sense for a CLI argument parsing library to defend against an input argument size overflowing
size_t. When the fuck would that ever happen?The PRs that actually fix a missed fallthrough causing undefined behavior look exactly the same as the ones that defend against somebody passing a 4GiB string as a CLI argument. They all have descriptions full of nothing but fluff, they all add much more code than they remove, they all bloat the code with more abstractions and indirections, and they all take way longer to review than the equivalent human-written code.
I'm even not against getting LLM contributions, but I'm getting sick of the fucking spam, and I'm losing patience with figuring out the difference between the two.
#LLM #LLMs #LLMSlop #AI #Spam #Code #Programming #PR #PullRequests #PullRequest
-
Getting a bit sick of fielding LLM PRs. I understand why many projects have a no-LLM policy. I'm generally fine getting good PRs, LLM-aided or not, but the poor ones are just complete wastes of time. They all read the same, good or not, so I have to spend quite a bit of time sussing through it to determine which ones are useless or not. They're all "bug fixes" or "security improvements".
No, it does not make sense for an CLI argument parsing library to scan through argv to make sure it doesn't contain null pointers. That's ridiculous. No, it does not make sense for a CLI argument parsing library to defend against an input argument size overflowing
size_t. When the fuck would that ever happen?The PRs that actually fix a missed fallthrough causing undefined behavior look exactly the same as the ones that defend against somebody passing a 4GiB string as a CLI argument. They all have descriptions full of nothing but fluff, they all add much more code than they remove, they all bloat the code with more abstractions and indirections, and they all take way longer to review than the equivalent human-written code.
I'm even not against getting LLM contributions, but I'm getting sick of the fucking spam, and I'm losing patience with figuring out the difference between the two.
#LLM #LLMs #LLMSlop #AI #Spam #Code #Programming #PR #PullRequests #PullRequest
-
🎮🤖 Apparently, PS3 emulator devs are drowning in AI-generated pull requests from wannabe vibecoders who think #debugging is a new TikTok dance. It seems the real "game" is getting human contributors who know that 'AI slop' isn't the latest fast-food trend. 🍔💻
https://kotaku.com/playstation-3-emulator-devs-politely-ask-that-people-stop-flooding-it-with-ai-code-pull-requests-2000694656 #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated -
🎮🤖 Apparently, PS3 emulator devs are drowning in AI-generated pull requests from wannabe vibecoders who think #debugging is a new TikTok dance. It seems the real "game" is getting human contributors who know that 'AI slop' isn't the latest fast-food trend. 🍔💻
https://kotaku.com/playstation-3-emulator-devs-politely-ask-that-people-stop-flooding-it-with-ai-code-pull-requests-2000694656 #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated -
Automate your PRs for seamless branch updates! Discover how to streamline code merges using GitHub Actions & Azure DevOps. https://www.funkysi1701.com/posts/2024/automatic-pull-requests/ #AzureDevOps #PullRequests #Automation #PowerShell #CI/CD #DevOps
-
Automate your PRs for seamless branch updates! Discover how to streamline code merges using GitHub Actions & Azure DevOps. https://www.funkysi1701.com/posts/2024/automatic-pull-requests/ #AzureDevOps #PullRequests #Automation #PowerShell #CI/CD #DevOps
-
و مازلنا في مجال ال
Office tools, #Collabora
عندو مشكلة مع
The Document Foundation
https://www.collaboraonline.com/blog/tdf-ejects-its-core-developers/
#Wayland
تتحصّل على إمكانيّة جديدة: من أعوام و كانت ثمّة حاجة ناقصة في
#Wayland
إلّي هي
#System #Restore
و إلّي مؤخّرا ولّات رسميّة
https://itsfoss.com/news/wayland-session-management/
أما زادة
#Wayland
تحصّل على تحسينات في حاجة أخرى، مثلا في ال
#Fractional #Scaling
https://www.phoronix.com/news/xx-fractional-scale-v2-MR-KWin
في مجال ال
#AI
Copilot
يحطّ
Ads
في ال
#PullRequests
و ال
#MergeRequests
https://www.neowin.net/news/microsoft-copilot-is-now-injecting-ads-into-pull-requests-on-github-gitlab/
https://www.techradar.com/pro/this-is-horrific-github-kills-copilot-pull-request-ads-after-user-backlash -
👨💻 Oh, look! Another gripping tale of an #ARM #developer lamenting the glacial pace of #RISC-V 🐌 while pretending to be productive with Fedora's bug circus. 🎪 But hey, at least he got 86 pull requests in—a testament to truly pioneering 🚀 the art of waiting around! 😂
https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/ #Fedora #pullrequests #productivity #HackerNews #ngated -
👨💻 Oh, look! Another gripping tale of an #ARM #developer lamenting the glacial pace of #RISC-V 🐌 while pretending to be productive with Fedora's bug circus. 🎪 But hey, at least he got 86 pull requests in—a testament to truly pioneering 🚀 the art of waiting around! 😂
https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/ #Fedora #pullrequests #productivity #HackerNews #ngated -
Oh look, someone wrote a whole #RFC to politely tell #AI to buzz off with their half-baked pull requests! 🤖🚫 Because, you know, humans have nothing better to do than babysit digital toddlers. Spoiler: If you found this page naturally, congrats, you get to ignore the nonsense! 🎉
https://406.fail/ #PullRequests #DigitalNonsense #TechHumor #HumanVsMachine #HackerNews #ngated -
Oh look, someone wrote a whole #RFC to politely tell #AI to buzz off with their half-baked pull requests! 🤖🚫 Because, you know, humans have nothing better to do than babysit digital toddlers. Spoiler: If you found this page naturally, congrats, you get to ignore the nonsense! 🎉
https://406.fail/ #PullRequests #DigitalNonsense #TechHumor #HumanVsMachine #HackerNews #ngated -
#PullRequests ≠ Code Reviews. Async PRs often delay delivery, drain trust & boost WIP. @javisan81 makes the case for sync reviews, pairing & post-merge feedback to ship faster with better quality—by building trust into the process.
Read: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
#PullRequests ≠ Code Reviews. Async PRs often delay delivery, drain trust & boost WIP. @javisan81 makes the case for sync reviews, pairing & post-merge feedback to ship faster with better quality—by building trust into the process.
Read: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
"Stacked PRs" is a proxy signal for failed engineering culture.
What you are saying is that you either can't/won't make a PR of reviewable size or that your team is incapable of getting reviewable PR's merged in a timely manner, and instead of fixing the problem you have taken the classic software engineering approach of adding an additional layer of complexity so now you have two problems
-
"Stacked PRs" is a proxy signal for failed engineering culture.
What you are saying is that you either can't/won't make a PR of reviewable size or that your team is incapable of getting reviewable PR's merged in a timely manner, and instead of fixing the problem you have taken the classic software engineering approach of adding an additional layer of complexity so now you have two problems
-
The PR author made changes! So at least it's not a "slop and forget" change.
However, all of their responses have that horrific obsequious tone of LLMs.
And one of my comments was "this call to openFile() seems to render the file, which would be inefficient for multiple files - can you just add it to the database instead?" and their response was "Good point, I've fixed it to be less complicated and more efficient"…
…and then they simplified the OTHER function (which did have more complex async for unexplained reasons)… and it STILL uses the function that I said was inefficient 🙄
Meanwhile, the comments on "this change seems unrelated" got "you're right, that was included by accident, I've reverted it".
I'm calling slop, and I hate the state of the world.
-
The PR author made changes! So at least it's not a "slop and forget" change.
However, all of their responses have that horrific obsequious tone of LLMs.
And one of my comments was "this call to openFile() seems to render the file, which would be inefficient for multiple files - can you just add it to the database instead?" and their response was "Good point, I've fixed it to be less complicated and more efficient"…
…and then they simplified the OTHER function (which did have more complex async for unexplained reasons)… and it STILL uses the function that I said was inefficient 🙄
Meanwhile, the comments on "this change seems unrelated" got "you're right, that was included by accident, I've reverted it".
I'm calling slop, and I hate the state of the world.
-
I've just read a PR on a FOSS project and… I think it's AI slop 😐
There's nothing much in the code that's blatant slop. It looks reasonable, give or take a weird choice on one function to call. But it's also a function that a human might naively decide to call.
But then there's the PR text. It has footnote-style links. And it says generic and unhelpful things like "swapped X for Y and updated Z"… Yes… I can see that from the diff. But WHY? 🙄
-
I've just read a PR on a FOSS project and… I think it's AI slop 😐
There's nothing much in the code that's blatant slop. It looks reasonable, give or take a weird choice on one function to call. But it's also a function that a human might naively decide to call.
But then there's the PR text. It has footnote-style links. And it says generic and unhelpful things like "swapped X for Y and updated Z"… Yes… I can see that from the diff. But WHY? 🙄
-
Finally #llm policies https://itsfoss.com/news/llvm-ai-policy/ It's gland to read this.
Certainly the #AI is a great tool that could help us in our jobs as #SoftwareEngineers but also I've read bad quality pull request from vibe coders that represent a bottle neck for the code review.
But the human in the loop policies that mentioned in the articles sound like a good start.
-
Finally #llm policies https://itsfoss.com/news/llvm-ai-policy/ It's gland to read this.
Certainly the #AI is a great tool that could help us in our jobs as #SoftwareEngineers but also I've read bad quality pull request from vibe coders that represent a bottle neck for the code review.
But the human in the loop policies that mentioned in the articles sound like a good start.
-
🚨 #GitHub threw a tantrum over #Issues and Pull Requests, and now they want us to subscribe for the thrill of OTP déjà vu 🎢🙄. If you ever wanted to be spammed by the world's largest code hoarder, your wish just came true! ✉️🤖
https://www.githubstatus.com/incidents/q987xpbqjbpl #PullRequests #Subscription #Drama #Spam #Alerts #HackerNews #ngated -
🚨 #GitHub threw a tantrum over #Issues and Pull Requests, and now they want us to subscribe for the thrill of OTP déjà vu 🎢🙄. If you ever wanted to be spammed by the world's largest code hoarder, your wish just came true! ✉️🤖
https://www.githubstatus.com/incidents/q987xpbqjbpl #PullRequests #Subscription #Drama #Spam #Alerts #HackerNews #ngated -
wow, @shlee made 12 PRs for Pixelfed yesterday <3
Great!
As an user and instance owner: THANK YOU. Shlee -
wow, @shlee made 12 PRs for Pixelfed yesterday <3
Great!
As an user and instance owner: THANK YOU. Shlee -
"We have a process to help us build in quality that is based on feedback and inviting human judgement, but if the system incentives constrain our ability to get the feedback, that also means we are less likely to build in quality."
#softwareengineering #pullrequests #vs #mobprogramming #classic
https://www.infoq.com/articles/co-creation-patterns-software-development/
-
"We have a process to help us build in quality that is based on feedback and inviting human judgement, but if the system incentives constrain our ability to get the feedback, that also means we are less likely to build in quality."
#softwareengineering #pullrequests #vs #mobprogramming #classic
https://www.infoq.com/articles/co-creation-patterns-software-development/
-
Wondering right now if coding agents will be the end of code reviews. They're already a bottleneck, and agents could multiply code output per developer significantly.
Feels like a better approach might be to "shift the review left": collaborate with the team on the spec upfront, then only run automated checks on PRs. 🤔
-
Wondering right now if coding agents will be the end of code reviews. They're already a bottleneck, and agents could multiply code output per developer significantly.
Feels like a better approach might be to "shift the review left": collaborate with the team on the spec upfront, then only run automated checks on PRs. 🤔
-
💼🎲 Ah yes, the age-old wisdom that uploading your spaghetti code to GitHub will magically transform you into a coding wizard just because everyone can now see your "brilliance." 🙄 Apparently, luck is now measured by the number of pull requests you receive on your half-baked projects. 🍀✨
https://github.com/readme/guides/publishing-your-work #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated -
💼🎲 Ah yes, the age-old wisdom that uploading your spaghetti code to GitHub will magically transform you into a coding wizard just because everyone can now see your "brilliance." 🙄 Apparently, luck is now measured by the number of pull requests you receive on your half-baked projects. 🍀✨
https://github.com/readme/guides/publishing-your-work #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated -
If you're serious about reducing lead time, rethink #PullRequests. They add async delays, inflate WIP & often fail to catch real issues. @javisan81 explains why trust-first teams review differently.
Read now: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
If you're serious about reducing lead time, rethink #PullRequests. They add async delays, inflate WIP & often fail to catch real issues. @javisan81 explains why trust-first teams review differently.
Read now: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
#Development #Techniques
Review your own Git pull requests · A simple habit can save many headaches later https://ilo.im/168cm6_____
#Programming #Coding #CodeReview #VersionControl #Git #GitHub #PullRequests #WebDev #Frontend #Backend -
#Development #Techniques
Review your own Git pull requests · A simple habit can save many headaches later https://ilo.im/168cm6_____
#Programming #Coding #CodeReview #VersionControl #Git #GitHub #PullRequests #WebDev #Frontend #Backend -
"The basic idea of doc bug zero, as I explained in Defining bug zero, is to clear out all the tickets in the doc issue queue, essentially to finish all your documentation work. Doing so would be the ultimate statement about the productivity gains from AI. Despite my attempts to get to bug zero, it still eludes me. I’m realizing that there’s an art to working through a bug queue, and AI can only take me so far. Good project skills are also needed. One of those skills, which I’ll address in this post, is making it easy for people to review the changelists, or pull requests. (The terminology used in my area of doc work is changelists, or CLs, so that’s how I’ll refer to them here.)"
https://idratherbewriting.com/blog/make-easy-to-review-changelists
#TechnicalWriting #SoftwareDocumentation #ZeroBugs #Changelists #PullRequests
-
"The basic idea of doc bug zero, as I explained in Defining bug zero, is to clear out all the tickets in the doc issue queue, essentially to finish all your documentation work. Doing so would be the ultimate statement about the productivity gains from AI. Despite my attempts to get to bug zero, it still eludes me. I’m realizing that there’s an art to working through a bug queue, and AI can only take me so far. Good project skills are also needed. One of those skills, which I’ll address in this post, is making it easy for people to review the changelists, or pull requests. (The terminology used in my area of doc work is changelists, or CLs, so that’s how I’ll refer to them here.)"
https://idratherbewriting.com/blog/make-easy-to-review-changelists
#TechnicalWriting #SoftwareDocumentation #ZeroBugs #Changelists #PullRequests
-
#PullRequests increase latency, not quality. Learn why async PRs hurt lead time—and what better code reviews look like.
Javier Lopez Fernandez on collaborative reviews, trust, and flow - read his #JAVAPRO article: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
#PullRequests increase latency, not quality. Learn why async PRs hurt lead time—and what better code reviews look like.
Javier Lopez Fernandez on collaborative reviews, trust, and flow - read his #JAVAPRO article: https://javapro.io/2025/10/29/pull-requests-code-reviews/
-
“Mistakes I See Engineers Making In Their Code Reviews”, Sean Goedecke (https://www.seangoedecke.com/good-code-reviews/).
Via HN: https://news.ycombinator.com/item?id=45701404
On Lobsters: https://lobste.rs/s/ngei5p/mistakes_i_see_engineers_making_their
#Programming #Reviews #CodeReviews #SeniorEngineers #SoftwareEngineering #Advice #PullRequests
-
“Mistakes I See Engineers Making In Their Code Reviews”, Sean Goedecke (https://www.seangoedecke.com/good-code-reviews/).
Via HN: https://news.ycombinator.com/item?id=45701404
On Lobsters: https://lobste.rs/s/ngei5p/mistakes_i_see_engineers_making_their
#Programming #Reviews #CodeReviews #SeniorEngineers #SoftwareEngineering #Advice #PullRequests
-
The Theatre of Pull Requests and Code Review
https://meks.quest/blogs/the-theatre-of-pull-requests-and-code-review
#HackerNews #Theatre #PullRequests #CodeReview #DeveloperCommunity #SoftwareEngineering