René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"New properties for closest tag message","articleBody":"### Describe the idea (required)\r\n\r\nProperties `commit.message.full` and `commit.message.short` are useful to get information about the last commit.\r\nBut it is often quite technical.\r\n\r\nIf you want a more general, semantic description, it is in the messages from annotated tags, for example, created with `git tag -a \u003ctagname\u003e -m \"Message for tag \u003ctagname\u003e...\"` .\r\n\r\nI would suggest to get the closest tag annotation and put it into new properties, for example, with names `closest.tag.message.full` and `closest.tag.message.short`.\r\n\r\n### Tell us about the expected behaviour (required)\r\n\r\nYou can get these messages with command `git tag` and option `-n`.\r\n\r\nMore specifically, when the user requests:\r\n- `closest.tag.message.full`: get the output of `git tag -n99 \u003ctagname\u003e` (full message, maximum 99 lines)\r\n- `closest.tag.message.short`: get the output of `git tag -n1 \u003ctagname\u003e` (only 1 line)\r\n\r\nIf the closest tag is not annotated, the `git` commands automatically get the message from the last git commit instead, therefore, this would be equivalent to `git.commit.message.*`.\r\n\r\n### Context (optional)\r\n\r\nA tag usually represents a new release or a new version of the code.\r\n\r\nWell used, an annotated tag message provides a practical way to convey a high-level summary over the content of this release.\r\n","author":{"url":"https://github.com/nxn-4-wdf","@type":"Person","name":"nxn-4-wdf"},"datePublished":"2024-03-06T17:21:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/109/git-commit-id-plugin-core/issues/109"}