From b4d33f3358d52677c1c08b486308960cfbd2f10e Mon Sep 17 00:00:00 2001 From: "https://christian.amsuess.com/chrysn" Date: Fri, 9 Jul 2021 15:26:13 +0000 Subject: [PATCH] Added a comment: +1 on supportunlocked in git-annex config --- ...omment_2_2973d438e8f3fda50cfb151534a8ec73._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/additional_git-annex-config_settings__63__/comment_2_2973d438e8f3fda50cfb151534a8ec73._comment diff --git a/doc/todo/additional_git-annex-config_settings__63__/comment_2_2973d438e8f3fda50cfb151534a8ec73._comment b/doc/todo/additional_git-annex-config_settings__63__/comment_2_2973d438e8f3fda50cfb151534a8ec73._comment new file mode 100644 index 0000000000..b9c837ba3e --- /dev/null +++ b/doc/todo/additional_git-annex-config_settings__63__/comment_2_2973d438e8f3fda50cfb151534a8ec73._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="https://christian.amsuess.com/chrysn" + nickname="chrysn" + avatar="http://christian.amsuess.com/avatar/c6c0d57d63ac88f3541522c4b21198c3c7169a665a2f2d733b4f78670322ffdc" + subject="+1 on supportunlocked in git-annex config" + date="2021-07-09T15:26:13Z" + content=""" +supportunlocked would definitely make sense; it can help protect against users accidentally checking in a file in the wrong mode even though it doesn't fit the repo's workflows. + +The alternative to setting this across all repos using git-annex config, at least in my workflows, would be to set a git hook to reject pushes (to master or synced/master) that contain unlocked files, but that sounds way more complex. +"""]] -- 2.39.5