[nuc1e0n]

In the corporate environments I've worked in it is often company policy that all commits to source code control should have messages that start with reference codes to the coresponding ticket in the issue tracker (often jira). This how I look up the whys and wherefores of code changes.

[FrostViper8]

A lot of places just don't do this. Unless there is a threat of a written warning some devs will do the bare minimum. I currently work with a guy that sometimes doesn't even run the code he checks in, I doubt he really knows how to code and everything is basically AI, management won't do anything and it the only remote job I could get. Another guy I work with won't do basic CSS fixes to things that are broken, so I cleaned up the login page for the site he is responsible for.

[nuc1e0n]

By whose judgement is the css you speak of 'broken'? Just making random code changes without a corresponding ticket is a recipe for troubles down the line. If you must do unprioritised work at the bare minimum create a issue tracker ticket to provide more information than can fit in a commit message. Something like selenium is good to automate acceptance testing (with screenshotting) cross browser as well.