This commit is contained in:
rinomizu5@5ead4c82685c65d7717dbd5591b80425036ae9e3 2022-08-04 08:26:11 +00:00 committed by admin
parent e91fdabba7
commit 925424092b

View file

@ -1,14 +1,13 @@
Hi, git-annex Team. Hi, git-annex Team.
I want to ask you this issue. I want to ask you this issue.
GIN is not recognized as a git-annex enabled repository when using the HTTPS protocol. 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 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. 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.
![image](https://user-images.githubusercontent.com/91708725/182578704-c04fdb60-5b6a-4faf-8869-04914723c27f.png)<br>
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. If there are any mistakes in my understanding please let me know.
sincerely yours, sincerely yours,
Rino Mizuguchi Rino Mizuguchi