Added a comment: +1 on supportunlocked in git-annex config
This commit is contained in:
parent
4a78debbe1
commit
b4d33f3358
1 changed files with 11 additions and 0 deletions
|
@ -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.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue