mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

muh

Browse source
This commit is contained in:
Joey Hess 2024-05-21 17:42:16 -04:00
parent 6c085cea9f
commit 6fe63e4615
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/forum/Strange_symlinkPointsToGitDir_error/comment_5_dad090743d2bacaac9106662354b68f0._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2024-05-21T21:34:12Z"
content="""
You will need to reach out to gitlab if you want to continue using it. They
need to set `git config receive.fsck.symlinkPointsToGitDir ignore`.
FWIW, github does not (currently) have this behavior.
This change does have some other knock-on effects that git-annex can deal
with, see [[todo/todo/deal_with_git_fsck_symlinkPointsToGitDir]].
I suppose that it would also work to unlock any annexed files that you want
to push to gitlab. It shouldn't matter that there are locked annexed files
in the history you've already pushed, only new commits in the push get
checked.
Using git-remote-gcrypt will also avoid the problem, since gitlab can't
tell that you're a scary symlink user if you encrypt everything. ;-)
"""]]