-
Notifications
You must be signed in to change notification settings - Fork 136
git-clone-to-dir.sh fails by default on newer git versions #3111
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.
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
Comments
[Triage] @crummel - please check if this affects the 6.0+ tarball creation infrastructure. If this only affects 3.1 we won't fix this given its EOL is December. |
[Triage] Per @crummel, this only affects 3.1 which is EOL shortly so we won't fix this. |
Also showing up in dotnet/aspnetcore#46174, we do need to fix this. |
@crummel any ETA on fixing this? Our source-build job is failing very frequently right now, it's causing a lot of disruption. Want to know if we should just disable it in the meantime. |
I've merged this in the Arcade main, 6.0, and 7.0 branches now. Matt Mitchell triggered the dependency flow in 7.0 so you should get that soon. |
Git has disallowed the
file
transport by default now sogit-clone-to-dir.sh
fails withfatal: transport 'file' not allowed
. The solution is eithergit config --global protocol.file.allow always
(for all clones on the machine) orgit -c protocol.file.allow=always clone <other stuff as usual>
(for the individual clone command).The text was updated successfully, but these errors were encountered: