Seems odd recommendation, even if someone does not need to commit direct on master, the repository itself as you stated in your first phrase is a DCVS, and by any means you have a "snapshot" from your remote (possibly origin but could be any upstream or fork ...).
A few examples you may consider keep master:
The same repository could be simply pushed for another remote servers without any connection with origin
You still can check on master even when offline or behind a network restriction
Can share your repo among process/tools that understand git in air-gaped environment (let's say test a ci pipeline without connections)
There is no real effort to keep your branch in-sync with your remote
Elliot mentioned about protected branch feature, which is something not "git native" but mostly of providers supports it, you can also check on git hooks to handle things agnostic to providers
If you delete your local master you still have references to the remote master. I don't see how a local master gets around air gaps or network restrictions, your local master can't be updated until git updates the origin/master branch.
Branch origin/master will always reflect the remote master branch after a fetch, even if a force push was done. The only exception to this is if your remote has a Master branch and you're on Windows.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Seems odd recommendation, even if someone does not need to commit direct on master, the repository itself as you stated in your first phrase is a DCVS, and by any means you have a "snapshot" from your remote (possibly origin but could be any upstream or fork ...).
A few examples you may consider keep master:
Elliot mentioned about protected branch feature, which is something not "git native" but mostly of providers supports it, you can also check on git hooks to handle things agnostic to providers
If you delete your local master you still have references to the remote master. I don't see how a local master gets around air gaps or network restrictions, your local master can't be updated until git updates the origin/master branch.
Branch origin/master will always reflect the remote master branch after a fetch, even if a force push was done. The only exception to this is if your remote has a Master branch and you're on Windows.