diff --git a/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn
new file mode 100644
index 0000000000..c569d3c283
--- /dev/null
+++ b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn
@@ -0,0 +1,14 @@
+Hi, git-annex Team.
+
+I want to ask you this issue.
+GIN is not recognized as a git-annex enabled repository when using the HTTPS protocol.
+
+I cloned a GIN repository with HTTPS protocol and then did `git annex init` on the cloned local repository, but it is not recognized as a git annex-enabled remote. 
+I checked the .git/config file and it says annex-ignore=true. 
+![image](https://user-images.githubusercontent.com/91708725/182578704-c04fdb60-5b6a-4faf-8869-04914723c27f.png)
+Because of this, git annex copy --to [GIN remote repository] is not possible with HTTPS protocol.
+
+If there are any mistakes in my understanding please let me know.
+
+sincerely yours,
+Rino Mizuguchi