Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document V4 regression on --change-permissions #809

Merged
merged 1 commit into from
Oct 1, 2023
Merged

Document V4 regression on --change-permissions #809

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions v3-to-v4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

### Manual: `--man`

Expand Down