From cd682cf227841b9d0efa922e0fc0c8eef9344342 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 1 Mar 2021 16:46:57 +0000 Subject: [PATCH] Added a comment: issue of pushing refs to annexed files but not info on how to fetch them --- .../comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents/comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment diff --git a/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents/comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment b/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents/comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment new file mode 100644 index 0000000000..ec912940ab --- /dev/null +++ b/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents/comment_3_7337c487d7118e0bfdf931a741f3d5a4._comment @@ -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. +"""]]