From e9d16de77a7346d777332e32e2abb3bcc7253858 Mon Sep 17 00:00:00 2001
From: kalmenn <kale@kalmenn.fr>
Date: Fri, 22 Dec 2023 00:56:16 +0100
Subject: [PATCH] .git-crypt/unlock.sh: Made clear that this script is only
 meant for me

---
 .git-crypt/unlock.sh | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.git-crypt/unlock.sh b/.git-crypt/unlock.sh
index 214297e..9ad9be1 100755
--- a/.git-crypt/unlock.sh
+++ b/.git-crypt/unlock.sh
@@ -5,6 +5,9 @@
 # config broken until the repo is decrypted.
 # However, decrypting with git-crypt unlock is not possible without a working
 # git config (it needs it to figure out which gpg key to use for decrypting)
+#
+# For now, this is hardcoded for my key. So if I ever give other people access,
+# I guess: TODO: decrypt using the first matching key in gpg, or throw an error
 
 git_crypt_key="/tmp/git-crypt_key.tmp";