git-annex's original design stored symlinks for all its annexed files, but recently they started defaulting to "unlocked" files -- meaning, files having their full contents on disk in place -- by adding a .gitattributes file that sets up git-annex smudge as a git filter. But there are cases where symlinks still show up -- all repos on https://github.com/OpenNeuroDatasets for example, or if you git annex init and git-annex decides your filesystem is "crippled" (i.e. doesn't have symlinks)). See https://git-annex.branchable.com/tips/unlocked_files/ and even https://git-annex.branchable.com/git-annex-adjust/ for more).
kousu
commented
1 year ago
git-annex's original design stored symlinks for all its annexed files, but recently they started defaulting to "unlocked" files -- meaning, files having their full contents on disk in place -- by adding a
.gitattributesfile that sets upgit-annex smudgeas a git filter. But there are cases where symlinks still show up -- all repos on https://github.com/OpenNeuroDatasets for example, or if yougit annex initand git-annex decides your filesystem is "crippled" (i.e. doesn't have symlinks)). See https://git-annex.branchable.com/tips/unlocked_files/ and even https://git-annex.branchable.com/git-annex-adjust/ for more).The current tests test for the "unlocked" case:
https://github.com/neuropoly/gitea/blob/de51980659cae2ef8d05c3766427c400933d92bd/integrations/git_annex_test.go#L755-L768
We should test the "locked" case as well.