Added a comment: +1 on supportunlocked in git-annex config

diff --git a/doc/todo/additional_git-annex-config_settings__63__/comment_1_74d61d6a4412223092f468628d3f2f45._comment b/doc/todo/additional_git-annex-config_settings__63__/comment_1_74d61d6a4412223092f468628d3f2f45._comment
new file mode 100644 (file)
index 0000000..a110770
--- /dev/null
+++ b/doc/todo/additional_git-annex-config_settings__63__/comment_1_74d61d6a4412223092f468628d3f2f45._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:25:53Z"
+ 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.
+"""]]