• leftytighty@slrpnk.net
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    28 days ago

    Worth noting that this is stored in the repository alongside the code changes and can be referenced in the future if someone is trying to understand that code or fix a bug in that code.

    For large projects spanning long periods of time sometimes the best way to find a bug’s cause is to scour the projects history to find out which commit caused the bug to appear, and if that commit doesn’t have a good description you’re unnecessarily disadvantaged when trying to find out why it caused the problem or what assumptions were going into the original code.