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.
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.
Keep changes small, we use git patch stack https://github.com/uptech/git-ps
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.
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.
Or maybe their IDE had a different auto indent config and they saved it all, then committed it all without checking the
diffor 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-formatas the Kate project has.That way the other devs don’t need to change their own IDE settings to comply.
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