-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Git fetch fails with too long branches since 2.48.1 #5476
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
A somewhat different issue (but also apparently a recent regression) is noted in jenkins-infra/helpdesk#4574 that does not involve particularly lengthy branch names or version paths or any other detail of the repository content: that if the path to the repo root is more than about 206 characters, the fetch fails just appending the length of a SHA (jenkins-infra/helpdesk#4574 (comment)):
|
The bug is still present with 2.49.0: even with the Git configuratiion For the record, it stopped working with 2.48.1, despite the settings specified in https://github.com/git-for-windows/git/blob/main/Documentation/config/core.adoc
|
/add relnote bug Git for Windows 2.48.1 introduced a regression when fetching long branches under The workflow run was started |
[Git for Windows 2.48.1 introduced a regression](git-for-windows/git#5476) when fetching long branches under `core.longPaths = true`, which [was fixed](git-for-windows/git#5550). Signed-off-by: gitforwindowshelper[bot] <gitforwindowshelper-bot@users.noreply.github.com>
Since git 2.48.1 i got issues when fetching long branches from a repository (usecase: The repository should be fetched by Jenkins, so path lengths get past 260 characters).
Steps to reproduce:
git init
git fetch --no-tags --force --progress --prune -- https://github.com/foo/bar.git +refs/heads/*:refs/remotes/origin/*
Expected result
Everything is fetched (When executing this with git 2.47.1 it works)
Actual Result
For the long branches i get these error messages:
The text was updated successfully, but these errors were encountered: