• Zeth0s@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    ·
    1 year ago

    We use sonarqube for code analysis that is pretty nice and has a community edition. It isn’t a bullet proof solution, but it is pretty convenient for maintainers and reviewers of PRs. The only thing missing from the enterprise edition are useless flashy dashboards to show to people who don’t understand computers

    • lowleveldata@programming.dev
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      I do have a Sonarqube server somewhere around. Is it considered an annoying behavior to scan an open source project and open issues for others to fix?

      • nutomic@lemmy.mlOPM
        link
        fedilink
        English
        arrow-up
        22
        ·
        1 year ago

        That depends, it would be annoying if you open lots of issues for minor, unimportant issues. But if you find a few major problems its good to report them. Of course its always ideal if you submit fixes as well, because there are never enough devs.

      • JoeKrogan@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        I think its better to detect something early even if there is not a fix as it at least can be triaged and others can fix it if the original reporter is unable to devote the time or whatever

      • Zeth0s@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        No, you are right… Time to hire 3 PMOs per developer to copy and paste random numbers in well formatted tables on outlook, and send it around in the mailing list with CIO and directors.

        And publicly shame developers if some meaningless number goes down

        /s