I personally prefer to share open reviews to a group of people than assigning it to a person directly. And I'm in camp "merge by the person which wrote the code" because I do believe it is a success moment.
There is more that could be part of the process e.g. the description of the review (providing screenshots, links to the tickets, etc) and also the size, the review should be as small as possible.
The last thing I want to mention is based on a comment from @kotzendekrabbe
: whatever your process is you should document it; make sure the whole team can look it up at any time.
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.
I personally prefer to share open reviews to a group of people than assigning it to a person directly. And I'm in camp "merge by the person which wrote the code" because I do believe it is a success moment.
There is more that could be part of the process e.g. the description of the review (providing screenshots, links to the tickets, etc) and also the size, the review should be as small as possible.
The last thing I want to mention is based on a comment from @kotzendekrabbe : whatever your process is you should document it; make sure the whole team can look it up at any time.