Drop chmod from setup; hook ships executable

2026-07-31 18:06:23 -04:00
parent 2b888f789e
commit 02fa93796c
2 changed files with 6 additions and 5 deletions
@@ -9,10 +9,10 @@
 # Enable after cloning:
 #
 #     git config core.hooksPath .githooks
-#     chmod +x .githooks/commit-msg
 #
-# The Gitea web API cannot set the executable bit, so the chmod is required
-# on first clone even though the file is committed.
+# The executable bit is committed (mode 100755), so a clone gets a runnable
+# hook. Git still will not enable a repo's hooks on its own — deliberately, so
+# that cloning cannot execute code from the remote — hence the one command.

 msg_file="$1"