• TerrorBite :veripawed3:@meow.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    @nthcdr this assumes that people write sensible and thorough commit messages, instead of brief five-word ones or, say, song lyrics. Both of which I’ve seen.

    I at least try, except maybe for the other day where my commit message consisted entirely of an exasperated “why”, followed by a revert.

    That being said, every commit message where I work is required to contain a ticket number (and the server will reject the push if you don’t) so at least there’s that for context.

    @257m @programming

    • nthcdr@emacs.ch
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      @TerrorBite

      Yes there need to be some assumption that your co-workers write reasonable commit message even if they have their lapses now and then.

      Another problem with comments in code is that they tend to be short because nobody likes to read code interspersed by walls of prose. But many times if something really needs explaining you also need a little more room doing it. Thus when committing in code people tend to gloss over important detail.

      Then of course there is literate programming. The other end of the spectrum, but then we’re talking code in documentation not comments in code.

      @257m @programming