You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/guided-workshop/exercises/3-codespaces.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ One thing that's really great is the [default dev container](https://github.com/
20
20
21
21
Let's create our own dev container! The [dev container is configured](https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers) by creating the Docker files Codespaces will use to create and configure the container, and providing any customizations in the `devcontainer.json` file. Customizations provided in `devcontainer.json` can include ports to open, commands to run, and extension to install in Visual Studio Code (either running locally on the desktop or in the browser). This configuration becomes part of the repository. All developers who wish to contribute can then create a new instance of the container based on the configuration you provided.
22
22
23
-
1. Access the Command Palette (<kbd>F1</kbd> or ☰ → View → Command Palette), then start typing **dev container**.
23
+
1. Access the Command Palette (<kbd>F1</kbd> or clicking ☰ → View → Command Palette), then start typing **dev container**.
24
24
1. Select **Codespaces: Add Development Container Configuration Files...** .
25
25
1. Select **Create a new configuration...**.
26
26
1. Select **From a predefined container configuration...**.
@@ -56,7 +56,7 @@ You've now defined a custom container!
56
56
57
57
Whenever someone uses the codespace you defined they'll have an environment with Node.js and Mongo DB, and the GitHub Copilot extension installed. Let's use this container!
58
58
59
-
1.Select <kbd>F1</kbd> to open the command palette.
59
+
1.Open the command palette.
60
60
1. Type **rebuild** and select **Codespaces: Rebuild container**.
61
61
1. Select **Rebuild Container** on the dialog box. Your container now rebuilds.
62
62
@@ -68,7 +68,7 @@ Custom containers for GitHub Codespaces become part of the source code for the r
68
68
69
69
> **IMPORTANT:** For purposes of this exercise we are pushing code updates directly to `main`, our default branch. Normally you would follow the [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow), which we will do in a [later exercise](6-github-flow.md).
70
70
71
-
1. Open the terminal window in the codespace by selecting <kbd>Ctl</kbd> + <kbd>`</kbd>.
71
+
1. Open the terminal window in the codespace by selecting <kbd>Ctl</kbd> + <kbd>`</kbd> or clicking ☰ → View → Terminal.
72
72
1. Find the issue number for defining the codespace by entering the following command:
0 commit comments