From 371238eca383d384cae3d5085e02cb97192bd1d1 Mon Sep 17 00:00:00 2001
From: alt <alt@web>
Date: Mon, 6 Dec 2021 15:56:56 +0000
Subject: [PATCH]

---
 doc/forum/conflict_with_git-crypt.mdwn | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 doc/forum/conflict_with_git-crypt.mdwn

diff --git a/doc/forum/conflict_with_git-crypt.mdwn b/doc/forum/conflict_with_git-crypt.mdwn
new file mode 100644
index 0000000000..0484ea5c87
--- /dev/null
+++ b/doc/forum/conflict_with_git-crypt.mdwn
@@ -0,0 +1,3 @@
+[git-crypt](https://www.agwa.name/projects/git-crypt/) is executed as a filter for secrets specified in `.gitattributes` files. However, git-annex initialization results in `* filter=annex` being added to `$GIT_DIR/info/attributes`, which [has the highest precedence](https://www.git-scm.com/docs/gitattributes#_description), ultimately causing any git-crypt filtering to be bypassed.
+
+Is there a recommended workaround for this? Thanks!