)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"1d8ab7bcf28aa6e6d516a42de44e4144b03fb6dc","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Parent:     8a42e0fe (Merge \"Add Playwright tests for audit template scope validation\")"},{"line_number":2,"context_line":"Author:     Chandan \u003cchkumar@redhat.com\u003e"},{"line_number":3,"context_line":"AuthorDate: 2026-10-29 19:37:57 +0530"},{"line_number":4,"context_line":"Commit:     Chandan \u003cchkumar@redhat.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1d86c651_c46ffbb1","line":1,"updated":"2026-11-12 04:25:22.000000000","message":"The commit message ends with two Change-Id footers: If99da9e53be6174d7f4c1698d6dd11a8f876bbae and If8c8e5b84e5b5fafd0218a24448c5e4da96ab6a3. A commit must carry exactly one Change-Id; Gerrit keys the review off the last footer and ignores the other. The stale duplicate (likely residue from cherry-picking or squashing the fix) permanently pollutes the commit history and is not caught by code linters.\n\n**Severity**: SUGGESTION | **Confidence**: 0.95\n\n**Impact**: Later inspection of the merged commit cannot tell which Change-Id identifies its Gerrit review, and tooling that parses Change-Id footers may associate the commit with the wrong review.\n\n**Recommendation**:\nAmend the commit message to keep only the Change-Id under which this Gerrit review is tracked (the last footer, If8c8e5b84e5b5fafd0218a24448c5e4da96ab6a3, is the one Gerrit uses) and delete the duplicate before merge.","commit_id":"6642fc0b454882c32539ca6adf168637ed72174c"}]}