Commit1fb363a

authored

Check the number of active codespaces before creating a new one in Step 3 (#94)

1 parent9ac889a commit1fb363aCopy full SHA for 1fb363a

File tree

-0

lines changed

-0

lines changed

Lines changed: 4 additions & 0 deletions

Original file line number	Diff line number	Diff line change
@@ -38,6 +38,10 @@ Let's customize some settings in the `devcontainer.json` file!
`38`	`38`	`1. Create a new codespace by navigating to the landing page of your repository.`
`39`	`39`	`1. Click theCode button located in the middle of the page.`
`40`	`40`	`1. Click theCodespaces tab on the box that pops up.`
	`41`	`+1. Ensure the number of active codespaces does not reach the maximum (typically 2). For more information, see[understanding the codespace lifecycle](https://docs.github.com/en/codespaces/getting-started/understanding-the-codespace-lifecycle).`
	`42`	`+`
	`43`	`+>Tip: To stop an active codespace, click the••• next to<span>●</span>Active and selectStop codespace from the menu.`
	`44`	`+`
`41`	`45`	`1. Click theCreate codespace on main button.`
`42`	`46`
`43`	`47`	`>Wait about2 minutes for the codespace to spin itself up.`

Comments

(0)