René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"GitHub pull-request workflow - use _expected_ commit hash","articleBody":"### Describe the idea (required)\r\n\r\nWhen running a GitHub pull-request workflow, the commit id is not the same as the pushed commit.\r\nhttps://github.com/orgs/community/discussions/25191\r\n\r\nMy use-case is when PR changes automatically deploy a micro-service, and I'd like my code to return the build's commit hash in an http response header, so developers and testers can confirm they are testing the right versions of our micro-services.\r\n\r\nI believe GitHub expects tools to work around/with GitHubs approach to finding the _appropriate_ commit id.  Is this a worthwhile feature to add to git-commit-id-maven-plugin ?\r\n\r\n\r\n### Tell us about the expected behaviour (required)\r\n\r\nI am expecting `git.commit.id/.full/.abbrev` to expose a commit-id that I can correlate with my git history.\r\n\r\nDuring GitHub pull-request worflows, GitHub runs on a 'merge' commit, which is not the pushed commit.\r\n(see https://github.com/orgs/community/discussions/25191)\r\n\r\n### Context (optional)\r\n\r\n_No response_","author":{"url":"https://github.com/nathan-summers-landg","@type":"Person","name":"nathan-summers-landg"},"datePublished":"2023-11-20T15:37:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/671/git-commit-id-maven-plugin/issues/671"}