How Kubernetes Broke Git

Re:How Kubernetes Broke Git by slavik81 on Sunday July 31, 2022 @03:06PM (#32297871)

I've convinced that the real problem with submodules is basically the UI. In particular, the defaults are terrible. You can ask it to block pushing if there are unpushed submodule commits with:

    git config push.recurseSubmodules check

Or you can make it push automatically by replacing "check" with "on-demand".

You may also find it helpful to make various commands automatically apply to submodules with:

    git config submodule.recurse true

[ Parent | on HN ]

Re:How Kubernetes Broke Git by mdaniel on Sunday July 31, 2022 @04:30PM (#32298542)

Thank you, that push.recurseSubmodules=check is the knob I was looking for, and wish it were the default

I got excited about the submodule.recurse=true one, but at least for "git status" it did not descend into the submodule the same way that "git submodule foreach git status" does

[ Parent | on HN ]