Course feedback

[cmwilson21]

We'd love to hear what you thought of this course! Please leave your feedback below and let us know!

[khoasv89]

After created the dev container file
Click the Create codespace on main button OR click the + sign on the tab. This will create a new codespace on the main branch. (Notice your other codespace listed here.)

Wait about 2 minutes for the codespace to spin itself up.

Verify that your new codespace is is running, as you did previously.

Note the image being used is the default image provided for GitHub Codespaces. It includes runtimes and tools for Python, Node.js, Docker, and more. See the full list here: https://aka.ms/ghcs-default-image. Your development team can use any custom image that has the necessary prerequisites installed. For more information, see codespace image.

Wait about 20 seconds then refresh this page (the one you're following instructions from). GitHub Actions will automatically update to the next step.
I've waited for 2 hours and nothing happen, can you please help ^^

[khoasv89]

i've resolved the problem, i think you should update the description that student can merge their PR to continue, thank you very much

[liebespaar93]

🚀 nice~ !

kyoulee! 🎓 seoul42 ~

[T1mL3arn]

I don't know what I did wrong, but the game did not start: bash: /usr/games/sl: No such file or directory. So I had to manually run apt-get commands from the codespace terminal to make things happen.

upd

Probably because of dotfiles settings. I fork the skills repo to organization profile, such profile does not allow to setup codespace the same way as a personal profile, and a personal profile allows to use only its own repos for dotfiles.

So this skill course should explicitly say in readme to use personal account.

[WwHeEnN]

I also run into the same issue with bash: /usr/games/sl: No such file or directory. And I am using a personal account. Still confused about how to resolve this.

[nubiannobody]

I had the same issue, the fix is to type the commands directly in the terminal as @T1mL3arn stated above. Thanks @T1mL3arn. After typing the commands in the terminal, first "sudo apt-get update" then "sudo apt-get install sl" type the command "/usr/games/sl" and then you can enjoy the show! :)

Last thing, I also made sure to select my repo after I enabled the dotfiles not sure if that helped or not but I did that step first.

[bttglc]

Fun, concise and useful! Thank you 🚀🐙

[davidcorcuera]

Good tutorial to understand the basics of codespaces.
As a recommendation in the tutorial, explain that only 2 started codespaces are allowed at the same time and that when creating another, you need to stop the others.

[2bitninja]

i got a lot of errors on my computer doing the training.
This codespace is currently running in recovery mode due to a configuration error. Please review the creation logs, update your dev container configuration as needed, and run the "Rebuild Container" command to rectify.

I think this had something to do with my mac having VS code installed and the the training wanting to launch in the app rather in that in the browser.

[YunusOganPXL]

everything works for me except for the last step bash: /usr/games/sl: No such file or directory this is what i get when i run /usr/games/s1 i tried manually running the setup.sh script didnt have permission so i added chmod+x now when i run the script i get sudo apt-get command not found i made sure the script has #!/bin/bash i can see the script in my repository and in vs code ive no clue what im doing wrong?

[Aishwarya-Verma]

We'd love to hear what you thought of this course! Please leave your feedback below and let us know!

What an amazing course! I liked it a lot, plus the hands-on exercises were just rightly designed. Thank you for the great intro on Codespaces, amazing GitHub feature 🤘

[GabCostta]

Gostaríamos de saber o que você achou deste curso! Por favor, deixe seu feedback abaixo e nos avise!

Achei muito legal novos aprendizados. contudo, fiquei preso na 4° etapa após usar o comando sl. O trem apareceu e o show deu certo. Porém, o repositório não atualizou para etapa 5.