diff --git a/88cc16386e4ab7b2cc83f760c34bc62f968718c5 b/88cc16386e4ab7b2cc83f760c34bc62f968718c5
new file mode 100644
index 0000000..4eca1a3
--- /dev/null
+++ b/88cc16386e4ab7b2cc83f760c34bc62f968718c5
@@ -0,0 +1,38 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "992f8c17_8d9953fe",
+        "filename": "/COMMIT_MSG",
+        "patchSetId": 1
+      },
+      "lineNbr": 17,
+      "author": {
+        "id": 36205
+      },
+      "writtenOn": "2024-02-20T19:14:05Z",
+      "side": 1,
+      "message": "Any tests for non-geo red configurations? i.e., to verify info message handled as expected (not printed) for changes in commands/v1/subcloud_manager.py",
+      "revId": "88cc16386e4ab7b2cc83f760c34bc62f968718c5",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "f27a05d1_7dba2e54",
+        "filename": "distributedcloud-client/dcmanagerclient/commands/v1/subcloud_peer_group_manager.py",
+        "patchSetId": 1
+      },
+      "lineNbr": 246,
+      "author": {
+        "id": 36205
+      },
+      "writtenOn": "2024-02-20T19:14:05Z",
+      "side": 1,
+      "message": "Are we only printing _info_message when it ends with new line (\\n)? Are you essentially checking if _info_message contains a string/valid string?",
+      "revId": "88cc16386e4ab7b2cc83f760c34bc62f968718c5",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}
\ No newline at end of file