From 7da482e001479511ca51e9bbd34b11c670ff0aa2 Mon Sep 17 00:00:00 2001 From: Tim Hockin Date: Tue, 19 Sep 2023 12:06:35 -0700 Subject: [PATCH] Add v4 note about change-permissions and exechook This is sort of a regression in v4 vs, v3, but ths use case is pretty niche, I think. --- v3-to-v4.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/v3-to-v4.md b/v3-to-v4.md index 9bb86d9..90bdee4 100644 --- a/v3-to-v4.md +++ b/v3-to-v4.md @@ -104,8 +104,15 @@ specified. The old `--change-permissions` flag was poorly designed and not able to express the real intentions (e.g. "allow group write" does not mean "set everything to -0775"). The new `--group-write` flag should cover what people ACTUALLY are -trying to do. The `--change-permissions` flag is no longer supported. +0775"). The new `--group-write` flag should cover what most people ACTUALLY +are trying to do. + +There is one case where `--change-permissions` was useful and `--group-write` +is not - making non-executable files in the repo executable so they can be run +as exechooks. The proper solution here is to make the file executable in the +repo, rather than changing it after checkout. + +The `--change-permissions` flag is no longer supported. ### SSH: `--ssh`