4 ms·
To nitpick, the git commit already contains information about which files are affected; adding it explicitly to the commit message does not add value and, like
by Cthulhu_ 3y ago
To nitpick, the git commit already contains information about which files are affected; adding it explicitly to the commit message does not add value and, like comments, may be incorrect. I like the angular style guide's concept of "scope", like, what category or module of the application does it apply to.
That said, an "utils" file is often a smell in code organization.
- forgotmypw17 3y ago> the git commit already contains information about which files are affected Right, but this is not always the same as the files which I intended to be affected, and the matching of the two is the sanity check here. utils was just an example filename.
- joshka 3y ago> the git commit already contains information about which files are affected; Contra: while this is true, it's worth considering how 'information about which files are effected' scales when examining the history of a repo. A commit message that simplifies and clarifies the intent is more useful than one that requires a future reader to read each git commit in full to understand the effect.