Git calls made while packaging your repo for the cloud cannot fetch or ask for passwords.
What's wrong with this entry?
Git invocations on the path that packages your repository for a cloud session now run with no network protocols allowed (GIT_ALLOW_PROTOCOL set to "none"), lazy fetching off, terminal credential prompts off, and bare repositories only when explicitly named. A hang waiting for a password or a surprise fetch is no longer possible there.
- The base argument list adds
safe.bareRepository=explicit. git status --porcelainnow always states an untracked-file mode, passing--untracked-files=normalwhen it is not asking for all of them, rather than relying on whatever the repository configures.- A new failure message covers the case where untracked files exceed the size budget for seeding.
GIT_ALLOW_PROTOCOL: "none",
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Git runs with a pinned environment and a blocked-flag list
Both mention allow protocol
-
v2.1.248
Control traffic survives a re-authentication instead of being dropped
Both mention protocol