When it's a "topic branch" (some stuff/features that you want to develop outside of master but that are really part of the "main development branch") then as soon as the code review has been done and the branch has been merged to master I almost always delete both the remote and the local branch. I cant remember that I've ever missed them later on, besides the commits are still there anyway, and it just reduces a lot of useless clutter which isn't helpful in any way.
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.
When it's a "topic branch" (some stuff/features that you want to develop outside of master but that are really part of the "main development branch") then as soon as the code review has been done and the branch has been merged to master I almost always delete both the remote and the local branch. I cant remember that I've ever missed them later on, besides the commits are still there anyway, and it just reduces a lot of useless clutter which isn't helpful in any way.