diff --git a/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__/comment_1_51e5f78a1cbd37598f3f0f6746df7320._comment b/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__/comment_1_51e5f78a1cbd37598f3f0f6746df7320._comment
new file mode 100644
index 0000000000..e944e69bc3
--- /dev/null
+++ b/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__/comment_1_51e5f78a1cbd37598f3f0f6746df7320._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-11-14T16:45:31Z"
+ content="""
+`git-annex sync --cleanup` does not do any of the pushing and pulling that
+`git-annex sync` does without the option. So you would want to run the
+command once without the option, and then once with it.
+
+Besides being extra work, `git-annex sync --cleanup` can delete sync
+branches that have not yet been merged. That's the point of it after all;
+the docs for it discuss a situation where you would want it to do that. But
+usually you do want to let the sync branches be merged.
+
+My recommendation would be to not use the option unless you actually need
+it.
+"""]]