1
0
mirror of synced 2025-12-19 18:10:59 -05:00

Introduce new variables for release phase terminology (#52375)

Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>
This commit is contained in:
Joe Clark
2024-09-27 09:41:15 -07:00
committed by GitHub
parent 58738e33ce
commit 8d452ebc55
185 changed files with 263 additions and 237 deletions

View File

@@ -27,7 +27,7 @@ There are currently two methods of accessing resources on a private network with
{% warning %}
**Warning**: The {% data variables.product.prodname_cli %} extension is deprecated and no longer supported.
**Warning**: The {% data variables.product.prodname_cli %} extension is {% data variables.release-phases.closing_down %} and is no longer supported.
{% endwarning %}

View File

@@ -256,7 +256,7 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
{% note %}
**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change.
**Note**: The {% data variables.product.prodname_cli %} extension is currently in {% data variables.release-phases.public_preview %} and subject to change.
{% endnote %}

View File

@@ -40,7 +40,7 @@ When you create a codespace, various steps happen in the background before the c
### Step 1: VM and storage are assigned to your codespace
When you create a codespace, a virtual machine (VM) is created using either the stable or beta release of the VM host image. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)." The host image defines the version of Linux that is used for the VM. The VM is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
When you create a codespace, a virtual machine (VM) is created using either the stable or {% data variables.release-phases.public_preview %} release of the VM host image. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)." The host image defines the version of Linux that is used for the VM. The VM is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
A [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) is then made of your repository, or of the template repository if you're creating a codespace from a template. This is cloned into the `/workspaces` directory of the VM and subsequently mounted into the dev container. For more information, see "[About the directory structure of a codespace](#about-the-directory-structure-of-a-codespace)" below.

View File

@@ -15,7 +15,7 @@ redirect_from:
{% note %}
**Note:** The {% data variables.codespaces.serverless %} editor is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/codespaces).
**Note:** The {% data variables.codespaces.serverless %} editor is currently in {% data variables.release-phases.public_preview %}. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/codespaces).
{% endnote %}