It is. Somewhat unnecessarily, too. Git already tracks changes so one can just roll back by checking out a previous commit point. Creating a new directory/clone each time doesn’t make sense; the manually modifying the config file adds complexity as well.
Nevertheless, I can understand and appreciate that some people have their workflows and live by them.
e: What I do is keep the git repo cloned and run from that. In
.git/hooks I’ve created a
post-merge script that runs automatically after a
git pull and updates permissions, etc. Separately, I have a cron job that just runs a git remote update on this clone and compares the hashes on the master branch and sends me an email with the commit log so I know there are changes. If the changes are important (security, bug fixes that affect me, etc.) I can login and run git merge (since the updates are already fetched), or git pull (if more updates have come in since the email). If the changes don’t affect me (like the recent plugin updates), I can ignore them for a few days.