@docwhat Can you give an example of a „file-path looking name“? You mean something like „git checkout update-entrypoint.sh“?

Unfortunately the testsuite isn‘t complete yet, so I will have to test such stuff manually. I remember that „git switch“ somehow didn‘t work a few months ago on GitHub Action.

This is a weird problem.
In 2019, there was an issue discussing the same problem. However in v2.1.0 this was fixed. (#6 (comment))

I could still reproduce the error and open #108. Just calling git fetch seems to solve the problem.
(I didn't use git switch as I'm not entirely sure if that could break the workflow of others)

The mentioned PR #108 has been merged. I will tag a new version soon.

As mentioned, I might switch to git switch at a future date after making sure the Action still works in all possible trigger combinations.

@docwhat Can you give an example of a „file-path looking name“? You mean something like „git checkout update-entrypoint.sh“?

git checkout pr/complex-branches

If you need to stick to using checkout, then the correct syntax is:

git checkout pr/complex-branches --

You may have seen this error message:

fatal: ambiguous argument 'pr/complex-branches': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'