From cde638f0743042b302f1c7678998e7629d87b16c Mon Sep 17 00:00:00 2001 From: github-actions Date: Thu, 2 Nov 2023 20:22:23 +0000 Subject: [PATCH] Update to X in STEP and README.md --- .github/steps/-step.txt | 2 +- README.md | 91 ++++++++++------------------------------- 2 files changed, 23 insertions(+), 70 deletions(-) diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt index b8626c4..62d8fe9 100644 --- a/.github/steps/-step.txt +++ b/.github/steps/-step.txt @@ -1 +1 @@ -4 +X diff --git a/README.md b/README.md index 0c9a3b1..3afdf2b 100644 --- a/README.md +++ b/README.md @@ -16,85 +16,38 @@ _Develop code using GitHub Codespaces and Visual Studio Code!_ -## Step 4: Personalize your codespace! +## Finish -_Nicely done customizing your codespace!_ :partying_face: +_Congratulations friend, you've completed this course!_ -When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. GitHub Codespaces offers two main ways of personalizing your codespace: `Settings Sync` with VS Code and `dotfiles`. +celebrate -`Dotfiles` will be the focus of this activity. +Here's a recap of all the tasks you've accomplished in your repository: -**What are `dotfiles`?** Dotfiles are files and folders on Unix-like systems starting with . that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on GitHub. +- You learned how to create a codespace and push code to your repository from the codespace. +- You learned how to use custom images in your codespace. +- You learned how to customize your codespace. +- You learned how to personalize your codespace. -Let's see how this works! +### Additional learning and resources -### :keyboard: Activity: Enable a `dotfile` for your codespace +- [Developing in a codespace](https://docs.github.com/en/codespaces/developing-in-codespaces/developing-in-a-codespace). Learn how to delete a codespace, open an existing codespace, connect to a private network, forward ports, and much more. +- [Set up your repository](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers). Learn how to set minimum machine specs for a codespace, add badges, set up a template repo, and much more. +- [Personalize and customize GitHub Codespaces](https://docs.github.com/en/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account). Learn how to use setting sync for your codespace, add dotfiles, set the default region, set the default editor, and much more. +- [Prebuild your codespace](https://docs.github.com/en/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds) +- [Manage your codespace](https://docs.github.com/en/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization) -1. Start from the landing page of your repository. -1. In the upper-right corner of any page, click your profile photo, and then click **Settings**. -1. In the **Code, planning, and automation** section of the sidebar, click **Codespaces**. -1. Under **Dotfiles**, select **Automatically install dotfiles** so that GitHub Codespaces automatically installs your dotfiles into every new codespace you create. -1. Click **Select repository** and then choose your current skills working repository as the repository from which to install dotfiles. +### What's next? -### :keyboard: Activity: Add a `dotfile` to your repository and run your codespace - -1. Start from the landing page of your repository. -1. Click the **Code** button located in the middle of the page. -1. Click the **Codespaces** tab on the box that pops up. -1. Click the **Create codespace on main** button. - - > Wait about **2 minutes** for the codespace to spin itself up. - -1. Verify your codespace is running. The browser should contain a VS Code web-based editor and a terminal should be present such as the below: - - ![codespace1](https://user-images.githubusercontent.com/26442605/207355196-71aab43f-35a9-495b-bcfe-bf3773c2f1b3.png) - -1. From inside the codespace in the VS Code explorer window, create a new file `setup.sh`. -1. Add the following code inside of the file: - - ```bash - #!/bin/bash - - sudo apt-get update - sudo apt-get install sl - ``` - -1. Save the file. - > **Note**: The file should autosave. -1. Commit the file changes. From the VS Code terminal enter: - - ```shell - git add setup.sh --chmod=+x - git commit -m "Adding setup.sh from the codespace!" - ``` - -1. Push the changes back to your repository. From the VS Code terminal, enter: - - ```shell - git push - ``` - -1. Switch back to the homepage of your repository and view the `setup.sh` to verify the new code was pushed to your repository. -1. Close the codespace web browser tab. -1. Click the **Create codespace on main** button. - - > Wait about **2 minutes** for the codespace to spin itself up. - -1. Verify your codespace is running, as you did previously. -1. Verify the `setup.sh` file is present in your VS Code editor. -1. From the VS Code terminal, type or paste: - - ```shell - /usr/games/sl - ``` - -1. Enjoy the show! -1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step. +- Learn more about securing your supply chain by reading: [GitHub Codespaces overview](https://docs.github.com/en/codespaces/overview). +- [We'd love to hear what you thought of this course](https://github.com/orgs/skills/discussions/categories/code-with-codespaces). +- [Learn another GitHub skill](https://github.com/skills). +- [Read the Get started with GitHub docs](https://docs.github.com/en/get-started). +- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).