)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"7606cd578449ec23111bad9fc1ea6ff9ea5952c3","unresolved":false,"context_lines":[{"line_number":9,"context_line":"and bc this , checking of this commit is failing"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"http://logs.openstack.org/61/661661/21/check/legacy-laravel-openstackid-unittests/f4ca6f3/job-output.txt.gz"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: I6e194bbc7ab5724551660fbc8ac0f01b304212e3"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"9fb8cfa7_89f2106f","line":12,"updated":"2019-07-03 03:45:54.000000000","message":"A few nits; a subject line and then a full, formatted paragraph without contractions, etc.  Just look at \"git log\" and follow along.\n\nLinks are ok, but this is not particularly useful for the commit message because it will disappear quickly as logs are cleaned up and commit messages are forever :)  pointing to a failing review, etc is probably more appropriate.","commit_id":"ba5f6649de9588529b451f86a20c8f32d201382e"}]}