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

Added a comment: issue of pushing refs to annexed files but not info on how to fetch them

Browse source
This commit is contained in:
Ilya_Shlyakhter 2021-03-01 16:46:57 +00:00 committed by admin
parent 324838324b
commit cd682cf227
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents/comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="issue of pushing refs to annexed files but not info on how to fetch them"
date="2021-03-01T16:46:56Z"
content="""
Just got burned by a (variation of) this issue, after coming back to git-annex after a break. This time, I did `git-annex-copy` the files to a remote, but forgot to `git-annex-sync` the new location information, so a new clone could not access the files. Maybe, a [pre-push hook](https://git-scm.com/docs/githooks#_pre_push) could be installed to print a warning (that can be turned off by a config setting), whenever you push refs to annexed files to a remote that has no (semi-)trusted location information for them? Basically, as a git user you get used to thinking that `git push` saves your work, and forgetting that it doesn't with `git-annex` can lead to data loss/inaccessibility.
"""]]