git switch is not a command
See original GitHub issueDescribe the Issue
Deploy fails with git switch is not a command
Logs
git switch develop
git: 'switch' is not a git command. See 'git --help'.
Workflow
https://github.com/GoldbarGames/GoldbarGames.github.io/blob/develop/.github/workflows/ci.yml
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Git: 'switch' is not a git command. See 'git --help' - GitLab Forum
I'm using GitLab 14.1.1 (community edition), while creating new projects ... cd X/ # git switch -c main git: 'switch' is not a...
Read more >git-switch Documentation - Git
git switch mytopic error: You have local changes to 'frotz'; not switching branches. You can give the -m flag to the command, which...
Read more >How can I switch to another branch in git? - Stack Overflow
If you just want to create a branch but not switch to it, use git ... First check out dev branch with command...
Read more >git switch - Switching branches | Learn Version Control with Git
The "switch" command provides a simple alternative to "checkout". It has a very clear and limited purpose: switching and creating branches!
Read more >git switch branch vs checkout - Bluecast Technologies
Git 2.23 came up with the new ' git switch ' command, which is not a new feature but an additional command to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The deploy now works!
The change to
git switch
along with the the documentation has been updated and released as part of3.1.4
I’ve also gone ahead and added an additional integration test that ensures that this workaround will continue to work should anything change with the ruby container.Thanks for the report!