From 7c014c651a1600a130513dee107805250bc7c3e3 Mon Sep 17 00:00:00 2001 From: dr0er Date: Wed, 16 Oct 2024 13:18:42 +0200 Subject: [PATCH] Adds periods to the end of each list line, as each line is a complete sentence --- ...-environment-variables-and-temporary-files.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/codespaces/developing-in-a-codespace/persisting-environment-variables-and-temporary-files.md b/content/codespaces/developing-in-a-codespace/persisting-environment-variables-and-temporary-files.md index b87fbce1955c..822685dd373c 100644 --- a/content/codespaces/developing-in-a-codespace/persisting-environment-variables-and-temporary-files.md +++ b/content/codespaces/developing-in-a-codespace/persisting-environment-variables-and-temporary-files.md @@ -2,8 +2,8 @@ title: Persisting environment variables and temporary files intro: You can configure custom environment variables so that they are set to the same value every time you open a codespace. You can also ensure that temporary files are not deleted when a codespace stops. versions: - fpt: '*' - ghec: '*' + fpt: "*" + ghec: "*" type: how_to topics: - Codespaces @@ -30,9 +30,9 @@ After you save the change to this file, the value will be set the next time you There are three ways that you can set persistent custom environment variables for all codespaces that you create for a repository: -* You can edit the `devcontainer.json` configuration file for the repository -* You can use a custom Dockerfile -* You can use development environment secrets +* You can edit the `devcontainer.json` configuration file for the repository. +* You can use a custom Dockerfile. +* You can use development environment secrets. #### Edit the `devcontainer.json` configuration file for the repository @@ -40,9 +40,9 @@ Edit the `devcontainer.json` configuration file for the repository, and use the ```json { - "remoteEnv": { - "VARNAME": "value" - } + "remoteEnv": { + "VARNAME": "value" + } } ```