@JPDev@programming.dev to Programmer Humor@programming.dev • 9 months agoReview Pleaseprogramming.devimagemessage-square112fedilinkarrow-up1992arrow-down117
arrow-up1975arrow-down1imageReview Pleaseprogramming.dev@JPDev@programming.dev to Programmer Humor@programming.dev • 9 months agomessage-square112fedilink
minus-square@ursakhiin@beehaw.orglinkfedilink5•9 months agoHuman 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.
minus-square@ErwinLottemann@feddit.delinkfedilink8•9 months agoyou should meet my coworker. this is one week worth of work. and he still only commit once a week.
minus-square@shiftymccool@programming.devlinkfedilink2•9 months agoThe 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
minus-square@ursakhiin@beehaw.orglinkfedilink1•9 months agoMany organizations vendor packages in the repo for a number of different reasons and languages. Not just for node.
minus-square@ulternolinkEnglish1•9 months agoOr 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.
minus-square@jjjalljs@ttrpg.networklinkfedilink3•9 months agoYou should have an agreed upon format that is enforced by cicd. Prettier, black, whatever.
minus-square@ulternolinkEnglish0•9 months agoI 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.
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.
you should meet my coworker. this is one week worth of work. and he still only commit once a week.
WHYYYY?
Relatable
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
Many organizations vendor packages in the repo for a number of different reasons and languages. Not just for node.
Or maybe their IDE had a different auto indent config and they saved it all, then committed it all without checking the
diff
or thestatus
.You should have an agreed upon format that is enforced by cicd. Prettier, black, whatever.
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.