points by schwede 1 day ago

Why does the commit editor hide the coauthored message? Why not pre-populate the text field and users take or leave it when committing?

dmitriv 1 day ago

I think this is a good point - perhaps there should be some commit-time UI which would let the user make the choice. Thanks for the suggestion!

jdlshore 1 day ago

Co-Authored-By is normally a trailer, and trailers aren’t part of the commit message. It’s likely the commit editor isn’t set up to show trailers. They’re not exactly obscure, but it does seem that they’re relatively unknown.

  • mplanchard 1 day ago

    What do you mean they aren’t part of the commit message? Trailers like (signed off by) are absolutely part of the message. Tools can choose to treat them as special metadata, but they’re part of the commit.

    The docs for the function to interpret trailers even says this explicitly: https://git-scm.com/docs/git-interpret-trailers

    > Add or parse structured information in commit messages

    • jdlshore 1 day ago

      I mean that they’re not necessarily part of the --message parameter to `git commit`, but instead part of the --trailer parameter. I don’t know how VSCode is programmed, but it seems plausible that trailers are handled separately from the message parameter.

      https://git-scm.com/docs/git-commit

      • baobabKoodaa 1 day ago

        We're talking about Git here. The question is not "how VSCode is programmed", the question is "does Git have a special field for commit trailers". The answer is no. Git stores the trailer as part of the commit message.

        • jdlshore 23 hours ago

          If you look at the comment I’m responding to, it is in fact about how VSCode is programmed; specifically, a possible reason why the Co-Authored-By trailer doesn’t show up in VSCode’s commit message box.