diff --git a/doc/tips/Using_git-worktree_with_annex/comment_1_8e1493eae66a483ece338649c763115a._comment b/doc/tips/Using_git-worktree_with_annex/comment_1_8e1493eae66a483ece338649c763115a._comment
new file mode 100644
index 0000000000..228205d4b4
--- /dev/null
+++ b/doc/tips/Using_git-worktree_with_annex/comment_1_8e1493eae66a483ece338649c763115a._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://christian.amsuess.com/chrysn"
+ nickname="chrysn"
+ avatar="http://christian.amsuess.com/avatar/c6c0d57d63ac88f3541522c4b21198c3c7169a665a2f2d733b4f78670322ffdc"
+ subject="worktrees vs. bare repositories"
+ date="2022-12-15T13:33:23Z"
+ content="""
+Note that while bare repos can have worktrees in git, the combination is not really supported in git-annex; as a result,
+
+* `git annex add` doesn't work (\"You cannot run this command in a bare repository.\") and
+* `git annex fix` would change all object links from two-character (`../.git/annex/objects/KP/4p/SHA256...`) to three-character (`../.git/annex/objects/7e3/613/SHA256...`) names.
+"""]]