I would lay down a list of standards that every member of the team should follow before committing the changes to the repository. The list could include stuff like:
Setting naming convention for variables, class, method, etc, so that code written by every member looks the same.
Fixing code alignment
Making the team aware of OOPS and SOLID principles when writing code. This makes a developer think thoroughly what part of the code belongs to what other parts.
Writing simple and readable code segments. Breaking down a complex/ a tall method into simple blocks can enhance readability and avoids potential bugs.
Code review on a timely basis. Making it a practice among team members is important.
Writing clean and consistent code is an art.
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 would lay down a list of standards that every member of the team should follow before committing the changes to the repository. The list could include stuff like:
Writing clean and consistent code is an art.