How Kubernetes Broke Git

Re:How Kubernetes Broke Git by tedmiston on Sunday July 31, 2022 @03:31PM (#32298060)

Are you saying submodule SHA was updated in the parent repo, but the new submodule commit which the parent repo is now pointing to was never pushed?

I haven't experienced that scenario before but it seems like there'd be an obvious git error?

[ Parent | on HN ]

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

No, the opposite:

    git clone --recursive some/repo.git
    cd repo/subrepo
    sed -i"" s/hello/goodbye/ README.md
    git commit -am 'lololo'
    cd ..
    git commit -am'subrepo with *local* sha reference'
    git status  # everything is clean!

now that I know that can happen, running `git submodule foreach git status` will surface the "your branch is ahead of" magic text that indicates what has gone on, but it would be tons better if the system understood what was happening and didn't allow such a bad outcome

[ Parent | on HN ]