The following was written by Hongzhe Zhou in August 2022 in response to
a problematic check-in using git. In order for others to avoid this,
please read this and make sure you avoid mistakes.

> I realized about it and when I tried to revert the commit it was not
> allowing me to commit the reverted changes (since one needs to use
> git push +--force).

No, you should never use "git push --force".
Just change back your file and submit it as a regular commit. Also the
best practice is to use "git pull --rebase" before committing, always.

> My understanding is that they just appear in my commit but if you
> check the modifications using 'blame' for example, it still shows the
> original person who did the modification.

Yes, but the problem is the "master" branch, which is the main history,
is now marked as being your history (see black color), while in fact it
was different before (now blue, former black). See the network graph:
The actual master branch now looks like a very long side development.

Furthermore, according to Wolfgang's "best practice guide" this
"destroys" all checked out SVN copies of the code. Even though I found
Wolfgang's statements about this SVN problems are not true for me.

Best greetings,