jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 11:26:57 -05:00
Code Issues Projects Releases Wiki Activity

Improve docs by removing typos and grammatical errors (#28391)

Browse Source 
Co-authored-by: Laura Coursen <lecoursen@github.com>
This commit is contained in:
Rockerz
2023-09-26 21:12:53 +05:30
committed by GitHub
parent de744d5df1
commit b625e5db46
6 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
View File

@@ -2,7 +2,7 @@
title: Testing dev container configuration changes on a prebuild-enabled branch
shortTitle: Test dev container changes
allowTitleToDifferFromFilename: true
intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace.
intro: When you change the dev container configuration for a branch that's enabled for prebuilds, you should test your changes in a codespace.
versions:
fpt: '*'
ghec: '*'
@@ -23,7 +23,7 @@ For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-c
1. In the codespace, check out a test branch. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)."
1. Make the required changes to the dev container configuration.
1. Apply the changes by rebuilding the container. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild for that branch.
1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch or an active feature branch, triggering an update of the prebuild for that branch.
{% note %}