)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"9978c75055c89b9c5158c6c7157c2c4cacf3ebe7","unresolved":true,"context_lines":[{"line_number":4,"context_line":"Commit:     kushalaa \u003ckushi.hande@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2022-09-18 17:31:24 -0700"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fixing Bug #1989817: Modified to show table instead of dict for --check"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: I5479c12ff97c12fbb5ab06d161d37b1dd736e8a2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"bb848e1e_646f4ac7","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":71},"updated":"2022-09-20 18:48:57.000000000","message":"you could improve the commit message a bit with some conventions we use around here. \n\nWe have automation that can link up the bug and update its status and such if you specified the bug reference in the \"body\" of the commit message, like this: \n\n Closes-Bug: #1989817\n \n \nLet the first line of the commit message be ~50 characters, while you\u0027re being as clear as possible -- so when someone is reading the summary of commit messages on this repositories, they get the intent without having to dig deeper... \n\nSo perhaps:\n\n \"Fix formatting of OSC server migration check-only\"\n \nor something along those lines. \n\nYou can add any further details in the commit message\u0027s body. Separate the Main commit line and its body by a blank line.. something along these lines:\n\n Fix formatting of OSC server migration check-only\n \n When the default table formatting is used, we can improve\n readability by transforming the capabilities dictionaries\n into paragraphs.\n \n Closes-Bug: #1989817\n \n\nIf you\u0027re interested in reading more about these commit message conventions, here\u0027s the long form: https://wiki.openstack.org/wiki/GitCommitMessages 😊 \nAnd from our own developer docs: https://docs.openstack.org/manila/latest/contributor/commit_message_tags.html","commit_id":"c25b8466865bbf3798c3abde809724d1c8fa956c"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"9978c75055c89b9c5158c6c7157c2c4cacf3ebe7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"5b1d500a_907022ea","updated":"2022-09-20 18:48:57.000000000","message":"Hi Kushalaa! Welcome to OpenStack! Thank you for pursuing this bug and getting it fixed up.\n\nFix looks great! Works well: https://paste.opendev.org/show/bB854NmPKipQLXvpk2gp/\n\nI just added a minor comments regarding the commit message inline, could you please take a look and update this patch?\n\nAlso, with your next update, could you please include a release note? A release note tells our users what was addressed in the next release. Here are some instructions on how to add such a note: \n\nhttps://docs.openstack.org/manila/latest/contributor/adding_release_notes.html#how-do-i-add-a-release-note\n\n","commit_id":"c25b8466865bbf3798c3abde809724d1c8fa956c"},{"author":{"_account_id":29632,"name":"Carlos Eduardo","email":"ces.eduardo98@gmail.com","username":"silvacarlos"},"change_message_id":"ef80fc42004fe92ba1c4f982271ef4e07f77d8a2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3cd4f58a_4aaa5079","updated":"2023-02-16 21:52:31.000000000","message":"LGTM, thanks!","commit_id":"05135dc1e27cea905f44e7443e7bea47872d0351"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"75cb9c00ea8913d6cf37cc310de2deccac099b5d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"8f655d3c_458ec8b5","updated":"2023-01-03 19:11:02.000000000","message":"recheck\n\nThanks for updating this patch, Kushalaa. The failure in the job isn\u0027t related to your fix; this re-run attempt should pass.. ","commit_id":"05135dc1e27cea905f44e7443e7bea47872d0351"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"c2ce85309ae85ee8596a2fe793f0cc5c3f835533","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"d1980a55_c0e31e8f","updated":"2023-01-11 20:53:16.000000000","message":"recheck\n\nthis failure\u0027s been sporadic","commit_id":"05135dc1e27cea905f44e7443e7bea47872d0351"}]}