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.
This commit is contained in:
parent
4ccf0633fb
commit
7da482e001
11
v3-to-v4.md
11
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`
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue