From 038bf11548ce1f58b7db04ebe61ba11d7a72dba9 Mon Sep 17 00:00:00 2001
From: pat <pat@web>
Date: Fri, 11 Nov 2022 22:46:11 +0000
Subject: [PATCH]

---
 ...__96__sync_--cleanup__96___by_default_a_bad_idea__63__.mdwn | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__.mdwn

diff --git a/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__.mdwn b/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__.mdwn
new file mode 100644
index 0000000000..8b3fb05a84
--- /dev/null
+++ b/doc/forum/Is___96__sync_--cleanup__96___by_default_a_bad_idea__63__.mdwn
@@ -0,0 +1,3 @@
+While going through the docs, I found that `sync --cleanup` will remove the `synced/*` branches after completing a sync.
+
+Is there any reason why it would be a bad idea to use that flag as a default for my own use. I like the clean aspect of not having those branches around, but I don't know if there's a good reason why I would want to keep them.