Added a comment: only for unlocked files?
authornobodyinperson <nobodyinperson@web>
Mon, 24 Mar 2025 18:37:31 +0000 (18:37 +0000)
committeradmin <admin@branchable.com>
Mon, 24 Mar 2025 18:37:31 +0000 (18:37 +0000)
doc/forum/git_assistant_creates_random_antagonistic_commits/comment_2_352d8910c4f31c52731adb8b25066c41._comment [new file with mode: 0644]

diff --git a/doc/forum/git_assistant_creates_random_antagonistic_commits/comment_2_352d8910c4f31c52731adb8b25066c41._comment b/doc/forum/git_assistant_creates_random_antagonistic_commits/comment_2_352d8910c4f31c52731adb8b25066c41._comment
new file mode 100644 (file)
index 0000000..d0bb5aa
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="nobodyinperson"
+ avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
+ subject="only for unlocked files?"
+ date="2025-03-24T18:37:31Z"
+ content="""
+I also see this very frequently in our shared family documents folder. Several people having the assistant running. I have a feeling it only happens for unlocked files, suggesting git clean/smudge filter nonsense is causing this. Looks like your files are also unlocked. Do you see any of this with locked files?
+"""]]