diff --git a/doc/bugs/howto_guarantee_a_single_instance_of_a_special_remote__63__/comment_7_987b2c1de4638e01c4f4feb028d47b88._comment b/doc/bugs/howto_guarantee_a_single_instance_of_a_special_remote__63__/comment_7_987b2c1de4638e01c4f4feb028d47b88._comment
new file mode 100644
index 0000000000..37d2103e0d
--- /dev/null
+++ b/doc/bugs/howto_guarantee_a_single_instance_of_a_special_remote__63__/comment_7_987b2c1de4638e01c4f4feb028d47b88._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 7"
+ date="2020-05-28T23:53:58Z"
+ content="""
+The workaround I had mentioned above originally seems to work fine for us, so indeed no need for this feature from DataLad side ATM.
+"""]]
diff --git a/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_3_47511f7b731cdefd108241bedb116f68._comment b/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_3_47511f7b731cdefd108241bedb116f68._comment
new file mode 100644
index 0000000000..6d03f3a72c
--- /dev/null
+++ b/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_3_47511f7b731cdefd108241bedb116f68._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="kyle"
+ avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3"
+ subject="comment 3"
+ date="2020-05-28T20:41:48Z"
+ content="""
+Joey, sorry for the misinformation, and thanks for the correction.
+"""]]