Git checkout pathspec error. Command to get the correct path

» git » Git checkout pathspec error. Command to get the correct path

By : jfinx

Date : January 12 2021, 07:00 PM

seems to work fine What am I trying to do: , Let me start with a question. You ran:

code :

git add app.py

git checkout sec_aggregator/feed/app.py

git checkout app.py

git checkout <some-commit-specifier> -- app.py

... <-F <-G <-H

...--F--G--H   <-- master

...--F--G--H   <-- master
            \
             I

...--F--G--H
            \
             I   <-- master

git checkout <hash-id> -- path/to/file

git show <hash-id>:path/to/file

...--F--G--H   <-- master
         \
          K--L   <-- test

...--F--G--H   <-- master, origin/master

...--F--G--H   <-- origin/master
            \
             I   <-- master

git show origin/master:feed/app.py

git checkout <commit> -- <path>

git show <commit>:<path>

Share :

Git - checkout a single directory out of a repo - error: pathspec [directory path] did not match any file(s) known to gi

By : Edy Santoso

Date : March 29 2020, 07:55 AM

this one helps. So after some back and forth in the comments, I think we've come to a solution here.
As it turns out, GIT does support the concept of checking out only subtrees of a given repository, through a process called 'sparse checkout' which you can find more information about here.

Installation via composer: multiple git remotes and pathspec error during feature branch checkout

By : P Vorobiev

Date : March 29 2020, 07:55 AM

I wish did fix the issue. Run git branch -a to see which branches you have.
It should look something like

code :

* master
remotes/origin/master
remotes/origin/branchname
remotes/composer/master

git fetch origin
git checkout --track origin/branchname

Git fetch does not resolve pathspec error on git checkout -- *

By : Oliver Baumbach

Date : March 29 2020, 07:55 AM

I think the issue was by ths following , I am afraid the linked question Git: cannot checkout branch - error: pathspec '...' did not match any file(s) known to git is a mess: as you noted, it has a lot of answers, and little explication. Meanwhile ElpieKay's comment has the right answer: node_modules is a file or directory that you are having your Git ignore, so when you ask your Git to update it, it says: Huh? Update what now?
The long description

code :

git checkout -- *

git checkout -- README hello node_modules ...

error: pathspec 'node_modules' did not match any file(s) known to git.

git checkout -- .

git checkout -- '*'

xargs with git checkout fails with pathspec error

By : SlowRiot23

Date : March 29 2020, 07:55 AM

To fix this issue From your question I conclude that you have a git repo with 3 branches solution-1, solution-2 & solution-3.
Now when you run the below command

code :

git checkout solution-1 && git checkout solution-2 && git checkout solution-3

git branch | grep solution- | cut -c 3- | xargs git checkout

git checkout solution-1 solution-2 solution-3

git branch | grep solution- | cut -c 3- | xargs -d '\n' -n1  git checkout

Git: cannot checkout branch - error: pathspec '...' did not match any file(s) known to git

By : Sezar Mbar

Date : March 29 2020, 07:55 AM

I think the issue was by ths following , Try git fetch so that your local repository gets all the new info from github. It just takes the information about new branches and no actual code. After that the git checkout should work fine.