Full Stack Developer from São Paulo, Brazil. I am a sociable introvert keen to develop great software and discuss how the various software we produce impact the world around us.
I think it is perfectly fine to reference tasks/stories on the commit message, and I personally think the best way to do this is by referencing it on the commit message body (with a link to the issue manager for instance). But it is important to keep in mind that this should be an additional information and it does not remove the need of good commit messages.
Another important point to be aware here is that doing that will create a coupling between the project's commit history and the issue manager that the team is using, so migrating to a different issue manager will be a lot harder and can make a great part of the commit message lose its meaning.
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 think it is perfectly fine to reference tasks/stories on the commit message, and I personally think the best way to do this is by referencing it on the commit message body (with a link to the issue manager for instance). But it is important to keep in mind that this should be an additional information and it does not remove the need of good commit messages.
Another important point to be aware here is that doing that will create a coupling between the project's commit history and the issue manager that the team is using, so migrating to a different issue manager will be a lot harder and can make a great part of the commit message lose its meaning.