This article aims to provide steps which should be used to clean up an integrated with vRealize Orchestrator remote Git repository, which contains files with special characters in their names, in case users would like to perform git clone or git pull operation against the repository.
Symptoms:
- When attempting to perform a git clone operation on your local Windows machine with your remote Git repository, which you have integrated with vRealize Orchestrator, you receive an error similar to
Cloning into '<repository>'…
remote: Enumerating objects: 44, done.
remote: Total 44 (delta 0), reused 0 (delta 0), pack-reused 44
Receiving objects: 100% (44/44), 4.50 KiB | 4.50 MiB/s, done.
Resolving deltas: 100% (4/4), done.
fatal: cannot create directory at '<path-to-an-object-with-special-characters-in-its-name>': Invalid argument
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
- When attempting to pull the latest changes on your local Windows machine from the working remote branch of your remote Git repository, which you have integrated with vRealize Orchestrator, you receive an error similar to
remote: Enumerating objects: 17, done.
remote: Counting objects: 100% (17/17), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 12 (delta 1), reused 2 (delta 0), pack-reused 0
Unpacking objects: 100% (12/12), 1.34 KiB | 17.00 KiB/s, done.
From <repository-url>
<commit-SHA-1>..<commit-SHA-2> <branch-name> -> <remote-name>/<branch-name>
fatal: cannot create directory at '<path-to-an-object-with-special-characters-in-its-name>': Invalid argument