When working in a team, I always use ticket number and description of a change, where change is always localized, not pushing 50 file changes in a single commit.
This allows me to go back to the ticket when looking at the code to see what were the exact requirements
Don't you just love seeing "WIP" and then 10+ file changed?
On a personal project, I always use some meaningful message, it just helps when looking at git blame and timeframes
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 working in a team, I always use ticket number and description of a change, where change is always localized, not pushing 50 file changes in a single commit.
This allows me to go back to the ticket when looking at the code to see what were the exact requirements
Don't you just love seeing "WIP" and then 10+ file changed?
On a personal project, I always use some meaningful message, it just helps when looking at git blame and timeframes