World map

 

BM

World 9: Power Tools

github.dev and Codespaces

You will learn: how to edit code in your browser, and when you need a cloud computer.

The problem

You are at a library computer. No Git, no code editor. Your README has a typo. Your teacher checks it in an hour.

Watch

Tap each point on the timeline.

On any repo page, press the . key. A code editor opens in your browser. This is github.dev: A code editor in your browser. Press . on a repo page to open it. It has no terminal.. It is free. You just need to be signed in.

Try it

github.dev looks like VS Code. Tap each glowing dot.

Tap the glowing dots to explore.

0 of 4 explored

Watch

bash
gh codespace create --repo aina-codes/diary
gh codespace code --web

github.dev has no terminal, so it can’t run code. Need that? Open a Codespace: A computer in the cloud, set up for your repo, with an editor and a terminal.: a cloud computer, set up for your repo. It needs a GitHub account and has usage limits.

Try it

Which one fits? Sort each card.

Drag a card into a box. Or tap the card, then tap the box.

      Predict

      You must run npm test before you push. Which one do you open?

      Check

      Good Codespace habit, or needs work? Swipe each one.

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 4

      Stop your Codespace when you finish

      You did it!

      You can now edit in a browser, or code in the cloud.

      Go deeper (optional)

      Press > instead of . to open github.dev in a new tab. Or change github.com to github.dev in the address bar. A Codespace can set itself up from a dev container file. Idle Codespaces stop by themselves after a while.