You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to clone this repo on windows, I've came across an error
error: invalid path '.github/pull_request_template.md.'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/
To Reproduce
Be on a Windows machine
Fork the repo
git clone %repo%
Expected behavior
The repository should be cloned
Solution
Obviously the issue lies on the .github/pull_request_template.md. file so if that file is removed, it should work fine. Otherwise, another possible alternative would be:
git init ToDo-iOS && cd ToDo-iOS
git config core.protectNTFS false
git remote add %repository_url%
git fetch
git checkout origin/master
The text was updated successfully, but these errors were encountered:
Hi @Guiguerreiro39, yes I suppose the error is due to pull_request_template.md. and deleting it shoulf fix the issues on windows. Thanks for pointing it out!
Would you like to work on this issue?
Hi @Guiguerreiro39, yes I suppose the error is due to pull_request_template.md. and deleting it shoulf fix the issues on windows. Thanks for pointing it out!
Would you like to work on this issue?
I can work on it.. is that file necessary for anything else?
yes so if you look carefully there are two files in .github directory, one is pull_request_template.md.second is PULL_REQUEST_TEMPLATE.md. You can delete the first one, the second one is being used for the template of pull requests.
Describe the bug
When trying to clone this repo on windows, I've came across an error
To Reproduce
Expected behavior
The repository should be cloned
Solution
Obviously the issue lies on the .github/pull_request_template.md. file so if that file is removed, it should work fine. Otherwise, another possible alternative would be:
The text was updated successfully, but these errors were encountered: