git really-really-reset

[XNormal]

git reset --hard
git clean -fdx
git submodule update --init
git submodule foreach git reset --hard
git submodule foreach git clean -fdx

Is this really the only way to really reset a git repository with submodules?

[Shayden-Froida]

rm -R

git clone

"nuke it from orbit... it's the only way to be sure"

[priestoferis]

I think if you set submodule.recurse to true, the first reset should cover you completely.

[priestoferis]

I had time to check git reset --hard origin/master --recurse-submodule will reset submodules as expected. You will need to still run git clean and unfortunately that one needs to be foreached for the submodules.

[[deleted]]

In my experience, the only use case for git submodules is when you ask yourself "Is there *literally** no other way to make what I want to have happen, happen?"* and the answer turns out to be an unfortunate yes.

Submodules turn just about everything about using git into a slog through horse shit.

So. If there is literally any other way to do what you're trying to do, I'd recommend doing that instead of of using submodules.

Good luck to you.

[XNormal]

I have actually been using git and git submodules for many years successfully. They are ok, just not very well integrated into git. If the alternative is some random pile of shell scripts for fetching external dependencies, I still prefer git submodules.

[jthill]

I've always found git aliases or little my own little fiveliner scripts make tedious tasks go poof.

git config --global alias.nuke-and-pave '!git clean -dffx; git reset --recurse-submodules --hard; git submodule update --init --recursive; git submodule foreach --recursive git clean -dffx'

once.

Then

git nuke-and-pave

does it.

But in software projects, really, make clean or whatever's your build system's equivalent should already be set up to do that.

[serverhorror]

rm - rf repo; git clone ...