home.social

#mergerequest — Public Fediverse posts

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

  1. idea regarding #code #review:
    intentionally adding #bugs into #code to check if the #reviewer discovers them.
    if the reviewer does not find them, then their #review is questionable.
    of course the added bugs should be removed before merging ;-)

    I am wondering if a concept like this already exists ...
    #codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

  2. idea regarding #code #review:
    intentionally adding #bugs into #code to check if the #reviewer discovers them.
    if the reviewer does not find them, then their #review is questionable.
    of course the added bugs should be removed before merging ;-)

    I am wondering if a concept like this already exists ...
    #codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

  3. idea regarding #code #review:
    intentionally adding #bugs into #code to check if the #reviewer discovers them.
    if the reviewer does not find them, then their #review is questionable.
    of course the added bugs should be removed before merging ;-)

    I am wondering if a concept like this already exists ...
    #codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

  4. idea regarding #code #review:
    intentionally adding #bugs into #code to check if the #reviewer discovers them.
    if the reviewer does not find them, then their #review is questionable.
    of course the added bugs should be removed before merging ;-)

    I am wondering if a concept like this already exists ...
    #codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

  5. idea regarding #code #review:
    intentionally adding #bugs into #code to check if the #reviewer discovers them.
    if the reviewer does not find them, then their #review is questionable.
    of course the added bugs should be removed before merging ;-)

    I am wondering if a concept like this already exists ...
    #codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

  6. RE: social.heise.de/@heiseonlineen

    My preferred solution here is CI/CD without code reviews, with 100% code responsibility and AI disclosure per merge request. Anyone using AI must first disclose this and then explain how it has been used. If the code causes a failure, I, and I alone, am liable for it, even at 23:55.

    #ai #llm #FckAI #FckLLMs #Amazon #MergeRequest #PullRequest #CICD #SoftwareDevelopment

  7. RE: social.heise.de/@heiseonlineen

    My preferred solution here is CI/CD without code reviews, with 100% code responsibility and AI disclosure per merge request. Anyone using AI must first disclose this and then explain how it has been used. If the code causes a failure, I, and I alone, am liable for it, even at 23:55.

    #ai #llm #FckAI #FckLLMs #Amazon #MergeRequest #PullRequest #CICD #SoftwareDevelopment

  8. Looking for resources on how to do good code reviews - technically, as a crafts-person, socially. Do you have suggestions?

    I would love to read a zine by @b0rk on the subject 😊

    One interesting article I recently read was “Understanding and Effectively Mitigating Code Review Anxiety” by @grimalkina and @CSLee. doi.org/10.1007/s10664-024-105

    #programming #codereview #softwareengineering #pullrequest #mergerequest

  9. When in doubt if your comment an a #PullRequest/ #MergeRequest/ #CodeReview or the like was substantial enough to be credited via a git trailer (e.g. Co-authored-by), what would you prefer that the other developer would do by default in that case?

    #amCoding #amProgramming #softwareEngineering #softwareDevelopment #git #gitTrailers

  10. @doctormo Never ever feel embarrassed about trying to uphold the standards that we've established!
    Remember: I show up in people's #mergerequest and point out that their commit messages aren't following our guidelines and that they need to fix them before a merge can happen. (So far they all appreciated the assistance.)

  11. Do you remember a couple of weeks ago when I complained that a very large #python contribution to #inkscape was poorly formatted and I felt embarrassed about pushing back and asking them to run a linter over it?

    Yeah I'm not fucking embarrassed now, I'm furious. 🤬

    Update: Apparently they meant a small section of it was, not the whole MR. I'm annoyed, but I'll have to take them at their word.

    #llm #oss #foss #mergerequest

  12. Vous Souhaitez savoir comment mettre en place une superbe #CI/#CD sur vos projets #Drupal avec #Gitlab, mais vous ignorez comment faire ? Alors, venez assister à ma conférence le 24 mai à l'@afup day de Lille et je vous dirai tout. #Déploiment #CodeQuality #MergeRequest

  13. Maybe this will be merged in #mastodon to facilitate the life of the admins when extending the default Toot/post size?

    github.com/mastodon/mastodon/p

    #opensource #mergerequest

  14. We found this by a fellow #Australia'n for the #FDroid site. Abandoned mid-2020 due to end of #covid lockdown and minor Git #MergeRequest (MR) issues.

    Forum (@fdroidorg):
    web.archive.org/web/2023102120

    MR:
    web.archive.org/web/2023102121

    Staged site (new dropdown menu):
    web.archive.org/web/2023102121

    Would anyone be interested in supporting us, as a #webDev, to implement the upgrade? Our instance needs funds to stay alive so we'd need (min) 3 donors giving $15/month while we volunteer.

    Boosts welcome.

    #foss

  15. @cassidyclown @JAJAX #mergerequest, fixed the one from froth to remove the black bg and made it small enough to federate
  16. Ever found yourself needing that one fix from a PR on GitHub that hasn’t been released yet? How can you get the code, for example a Magento fix, into your code base? Copy-paste it? That might work for small changes, but for large and complex changes copy-pasting is no solution. Luckily, we can use GitHub to generate a patch file, which can then be applied with […]

    https://kevingimbel.de/blog/2020/12/550/