kubernetes
/
git-sync
mirror of https://github.com/kubernetes/git-sync.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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:
Tim Hockin 2023-09-19 12:06:35 -07:00
parent 4ccf0633fb
commit 7da482e001
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
v3-to-v4.md
View File

@ -104,8 +104,15 @@ specified.
The old `--change-permissions` flag was poorly designed and not able to express 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 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 0775"). The new `--group-write` flag should cover what most people ACTUALLY
trying to do. The `--change-permissions` flag is no longer supported. 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` ### SSH: `--ssh`