Code is evergreen, whereas a git commit represents a change at a single point in time. It will always be limited by the knowledge the author had available to th

Code is evergreen, whereas a git commit represents a change at a single point in time. It will always be limited by the knowledge the author had available to them. The commit message from 2020 with suggested alternatives might very well go stale. Does the author go and force a noop commit so they can document new best practice in a new commit message?