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

    Oddly enough the folks I work with are really good at the Jira ticket thing and frankly it’s much more useful than “feat” prefixes on everything. Because the Jira ticket gives me a “why” which can be amazingly helpful when trying to figure out “why was this line added”.

    I have never once found feat/fix/chore to be of any use when looking at history. It’s useless noise.

    • nebeker@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      14 hours ago

      I’m OK with Jira ticket for branch names and pull requests. If something needs paragraphs to explain it, it should be a ticket. By all means copy that to the pull request and then have it in the merge (or squash commit).

      If fact, I think I’ll suggest we automate that in my org - we’ve lived through a TFS to Jira migrations and it’s a lot harder to track down the original info now. If you migrate from GitHub to GitLab or ForgeJo, that’s one more layer of business knowledge and motivation that gets lost.

      Either way, I’m on board with a simple “Fixed API routing” or “Improved Artist card reflow” message. If I’m reading it, I’m already looking at the routes or the CSS.

    • morbidcactus@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      One thing I’ve found useful with some git forges (haven’t tried them all so no idea if it’s universal) is tagging commits to issues and/or prs. Never bothered with the auto close functionality but assuming people actually put details into tickets, it’s come in handy a bunch of times this year to figure out why something got implemented when the original contributor is long gone.