• ursakhiin@beehaw.org
      link
      fedilink
      arrow-up
      5
      ·
      7 months ago

      Human made changes is likely not what caused this image to occur.

      111 files with that kind of change count is most likely a dependency update. But could also be that somebody screwed up a merge step somewhere.

      • shiftymccool@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        The only way I see that is a dependency update is if you’re versioning your node_modules or <insert-folder-here> which is generally a no-no

        • ursakhiin@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          Many organizations vendor packages in the repo for a number of different reasons and languages. Not just for node.

      • ulterno@lemmy.kde.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        Or maybe their IDE had a different auto indent config and they saved it all, then committed it all without checking the diff or the status.

          • ulterno@lemmy.kde.social
            link
            fedilink
            English
            arrow-up
            0
            ·
            7 months ago

            I do like the idea of mandating git clang-format as the Kate project has.
            That way the other devs don’t need to change their own IDE settings to comply.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      I’m still annoyed that Github doesn’t have good support for stacked diffs. It’s still not possible to say that one PR depends on a different one, and still has no ability to review and land them as a stack.