home.social

#pullrequests — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pullrequests, aggregated by home.social.

  1. 🎮🤖 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. 🍔💻
    kotaku.com/playstation-3-emula #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated

  2. 🎮🤖 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. 🍔💻
    kotaku.com/playstation-3-emula #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated

  3. 🎮🤖 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. 🍔💻
    kotaku.com/playstation-3-emula #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated

  4. 🎮🤖 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. 🍔💻
    kotaku.com/playstation-3-emula #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated

  5. 🎮🤖 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. 🍔💻
    kotaku.com/playstation-3-emula #PS3Emulator #AIgenerated #PullRequests #GameDevelopment #HackerNews #ngated

  6. Automate your PRs for seamless branch updates! Discover how to streamline code merges using GitHub Actions & Azure DevOps. funkysi1701.com/posts/2024/aut /CD

  7. و مازلنا في مجال ال
    Office tools, #Collabora
    عندو مشكلة مع
    The Document Foundation
    collaboraonline.com/blog/tdf-e
    #Wayland
    تتحصّل على إمكانيّة جديدة: من أعوام و كانت ثمّة حاجة ناقصة في
    #Wayland
    إلّي هي
    #System #Restore
    و إلّي مؤخّرا ولّات رسميّة
    itsfoss.com/news/wayland-sessi
    أما زادة
    #Wayland
    تحصّل على تحسينات في حاجة أخرى، مثلا في ال
    #Fractional #Scaling
    phoronix.com/news/xx-fractiona
    في مجال ال
    #AI
    Copilot
    يحطّ
    Ads
    في ال
    #PullRequests
    و ال
    #MergeRequests
    neowin.net/news/microsoft-copi
    techradar.com/pro/this-is-horr

  8. 👨‍💻 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! 😂
    marcin.juszkiewicz.com.pl/2026 #Fedora #pullrequests #productivity #HackerNews #ngated

  9. 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! 🎉
    406.fail/ #PullRequests #DigitalNonsense #TechHumor #HumanVsMachine #HackerNews #ngated

  10. #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: javapro.io/2025/10/29/pull-req

    #Agile #Java

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

    #programming #pullrequests

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

    #FuckGenAI #DriveBySlopping #PullRequests #EngageYourBrain

  13. 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? 🙄

    #FuckGenAI #PullRequests #EngageYourBrain

  14. Finally #llm policies itsfoss.com/news/llvm-ai-polic 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.

    #openSource #pullRequests #quality #programming #coding

  15. Finally #llm policies itsfoss.com/news/llvm-ai-polic 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.

    #openSource #pullRequests #quality #programming #coding

  16. Finally #llm policies itsfoss.com/news/llvm-ai-polic 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.

    #openSource #pullRequests #quality #programming #coding

  17. Finally #llm policies itsfoss.com/news/llvm-ai-polic 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.

    #openSource #pullRequests #quality #programming #coding

  18. 🚨 #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! ✉️🤖
    githubstatus.com/incidents/q98 #PullRequests #Subscription #Drama #Spam #Alerts #HackerNews #ngated

  19. wow, @shlee made 12 PRs for Pixelfed yesterday <3

    Great!
    As an user and instance owner: THANK YOU. Shlee

    #pixelfed #pullrequests

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

    infoq.com/articles/co-creation

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

    #ai #codingagents #pullrequests

  22. 💼🎲 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. 🍀✨
    github.com/readme/guides/publi #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated

  23. 💼🎲 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. 🍀✨
    github.com/readme/guides/publi #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated

  24. 💼🎲 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. 🍀✨
    github.com/readme/guides/publi #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated

  25. 💼🎲 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. 🍀✨
    github.com/readme/guides/publi #spaghetticode #codingwizard #pullrequests #luckinprogramming #halfbakedprojects #HackerNews #ngated

  26. 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: javapro.io/2025/10/29/pull-req

    #SoftwareEngineering #Agile #CodeReview #Java

  27. "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.)"

    idratherbewriting.com/blog/mak

    #TechnicalWriting #SoftwareDocumentation #ZeroBugs #Changelists #PullRequests

  28. #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: javapro.io/2025/10/29/pull-req

    #SoftwareEngineering #Agile #CodeReview

  29. Today was #rage and #pullrequests.

    1. Yes, #hardcoded #opaque identifiers are a little tiny bit faster in this task that runs for a couple of minutes on an irregular, on-demand basis. But maybe you should look up those monstrosities starting from their #humanfriendly equivalents which are much more descriptive.

    2. Fine, you wrote some #shellscript with #LLM. It's not very #DRY and it interfaces poorly with the #pipeline syntax. This will require #commits to a branch, not just a #review.

  30. Just published two new scripts to scratch a long-standing itch.

    When working with on , I like cleanly separated small commits. I then review commit-by-commit, but github does not show on comments what commit it was made against. My script adds this info automatically when adding a comment.

    The second script just adds e.g. "3 / 5" when viewing the 3rd commit in a 5-commit PR, to see how far along I am :-)

    greasyfork.org/en/scripts/5493 and
    greasyfork.org/en/scripts/5493

  31. If your pull requests look like "do this, do unrelated that, do more unrelated stuff", maybe, just maybe, you should consider not requiring pre-merge approvals ;)

    #SoftwareEngineering #SoftwareDevelopment #PullRequests #Git #GitHub

  32. Naty @eclecticpassions ·

    Learning about git pull requests and branches... I might be making my first PR soon on two projects. (One is ReTex the Markdown editor, and the other is my current Hugo theme: anubis2). Excited. Hope I get the process right! I'm writing a follow up post on too. Really looking forward to sharing it!

  33. Learning about git pull requests and branches... I might be making my first PR soon on two projects. (One is ReTex the Markdown editor, and the other is my current Hugo theme: anubis2). Excited. Hope I get the process right! I'm writing a follow up post on #retext too. Really looking forward to sharing it!

    #git #pullrequests #markdown #markdowneditor #pythonapps

  34. Learning about git pull requests and branches... I might be making my first PR soon on two projects. (One is ReTex the Markdown editor, and the other is my current Hugo theme: anubis2). Excited. Hope I get the process right! I'm writing a follow up post on #retext too. Really looking forward to sharing it!

    #git #pullrequests #markdown #markdowneditor #pythonapps

  35. Learning about git pull requests and branches... I might be making my first PR soon on two projects. (One is ReTex the Markdown editor, and the other is my current Hugo theme: anubis2). Excited. Hope I get the process right! I'm writing a follow up post on #retext too. Really looking forward to sharing it!

    #git #pullrequests #markdown #markdowneditor #pythonapps

  36. Learning about git pull requests and branches... I might be making my first PR soon on two projects. (One is ReTex the Markdown editor, and the other is my current Hugo theme: anubis2). Excited. Hope I get the process right! I'm writing a follow up post on #retext too. Really looking forward to sharing it!

    #git #pullrequests #markdown #markdowneditor #pythonapps

  37. Automating Code Compliance: AI-Driven Code Style Enforcement for Pull Requests dlvr.it/THkbYx via PlanetPowerShell #CodeCompliance #AIDriven #GitHub #PullRequests

  38. Automating Code Compliance: AI-Driven Code Style Enforcement for Pull Requests dlvr.it/THkbYx via PlanetPowerShell #CodeCompliance #AIDriven #GitHub #PullRequests

  39. Automating Code Compliance: AI-Driven Code Style Enforcement for Pull Requests dlvr.it/THkbYx via PlanetPowerShell #CodeCompliance #AIDriven #GitHub #PullRequests

  40. Automating Code Compliance: AI-Driven Code Style Enforcement for Pull Requests dlvr.it/THkbYx via PlanetPowerShell #CodeCompliance #AIDriven #GitHub #PullRequests

  41. Automating Code Compliance: AI-Driven Code Style Enforcement for Pull Requests dlvr.it/THkbYx via PlanetPowerShell #CodeCompliance #AIDriven #GitHub #PullRequests