• atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    23 hours ago

    The customer receives a list of feat and fix commit titles as info with a release.

    The problem is that the language customers want and the language developers want are different things. Abusing commit messages to try to create documentation is just a bad idea. Spend a few mins to summarize for your users what has changed. You should be able to pull the tickets that went into a release for that pretty easily. Hell have AI do it if you’re that lazy. But as a developer I want to know what your commit did. Just explain your change in a way that will help me later on.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      I find a commit message describing consequential effect and intended goal/change more useful than technical details. And those are usually what the customer cares about. “function/action works again” “fix x by y” “introduce functionality x”.

      But as a developer I want to know what your commit did.

      I agree. I don’t see them as opposites or contradicting to pulling them. Either as a free information forward, or as a basis for describing it into something a customer understands, or into what is notable about a release.