SAP-samples / SAP-samples/leanix-integration-api-examples
cannot pull on windows due to file names
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
cannot pull anymore on windows, probalby due to : in name
error: invalid path 'IntegrationAPI-workshop/Task-1:CreateApplication/Config1_CreateApplication.json'
error: invalid path 'IntegrationAPI-workshop/Task-1:CreateApplication/README.md'
error: invalid path 'IntegrationAPI-workshop/Task-1:CreateApplication/input.json'
error: invalid path 'IntegrationAPI-workshop/Task-2:Update-BusinessCriticality/README.md'
error: invalid path 'IntegrationAPI-workshop/Task-2:Update-BusinessCriticality/config.json'
error: invalid path 'IntegrationAPI-workshop/Task-2:Update-BusinessCriticality/input.json'
error: invalid path 'IntegrationAPI-workshop/Task-3:ApplyCustomFields/README.md'
error: invalid path 'IntegrationAPI-workshop/Task-3:ApplyCustomFields/config.json'
error: invalid path 'IntegrationAPI-workshop/Task-3:ApplyCustomFields/input.json'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the listed IntegrationAPI-workshop paths, especially directory names containing colons, and reproduce the pull on Windows. Check which filenames Git rejects on Windows; done means the repository can be cloned or pulled there without invalid-path errors while the workshop files remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100