I'm surprised that no one said it, the article's advice of routinely deleting your local repository, without first making a copy, is terrible!!!
You lose your whole reflog and all the unreachable commits that way, and so some errors you might make will lead to unrecoverable losses..!
If you want do begin from a new clone from time to time, but make copies of the old local repository first, and keep them around!
You're bound to lose work occasionally, otherwise.
And why even messing around with a remote repository and force pushes, to safeguard yourself from rebase problems you can simply take a local copy of the repository..!
That's of course when it's not a huge repository
An alternative to keep in mind is to use local clones, updating which will take less time than taking a full copy.
You lose your whole reflog and all the unreachable commits that way, and so some errors you might make will lead to unrecoverable losses..!
If you want do begin from a new clone from time to time, but make copies of the old local repository first, and keep them around! You're bound to lose work occasionally, otherwise.
And why even messing around with a remote repository and force pushes, to safeguard yourself from rebase problems you can simply take a local copy of the repository..!
That's of course when it's not a huge repository
An alternative to keep in mind is to use local clones, updating which will take less time than taking a full copy.