git undo hundreds of not pushed add & commits

[freedom-foundation]

The overall purpose of this question is to undo hundreds of not pushed add & commits without deleting any of the "shallow" file tree (the original files not yet pushed).

What is the difference between a git reset --soft and a blank which is --mixed ? Does this from --soft: "leaves all your changed files "Changes to be committed", as git status would put it.'" mean soft leaves the adds indexed but before the adds were commit and without commit whereas --mixed would erase the index having adds ready to commit? This is how I gather it however the manpage hint's at being written by a thirdparty and having conflicting and scattered jargon makes it to where the user cannot communicate in a meaningful way about using the software. The difference here is touching the index but what does that mean in pragma: what does a git repo index handle? Isn't there some better way to find answers rather than Google advertisements or IRC wrong answers. See the snippet from the manpage below:

git reset [] []
This form resets the current branch head to and possibly
updates the index (resetting it to the tree of ) and the
working tree depending on . Before the operation, ORIG_HEAD
is set to the tip of the current branch. If is omitted,
defaults to --mixed. The must be one of the following:

       --soft
           Does not touch the index file or the working tree at all (but
           resets the head to <commit>, just like all modes do). This
           leaves all your changed files "Changes to be committed", as
           git status would put it.

       --mixed
           Resets the index but not the working tree (i.e., the changed
           files are preserved but not marked for commit) and reports
           what has not been updated. This is the default action.

           If -N is specified, removed paths are marked as intent-to-add
           (see git-add(1)).

from A_bughunter@proton.me

Sent with Proton Mail secure email.