Document codespaces timeout setting (#23107)

Co-authored-by: Allison Weins <3174849+2percentsilk@users.noreply.github.com>
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>

Author: 3 people

assets/images/help/codespaces/setting-default-timeout.png

@@ -14,6 +14,7 @@ children:
   - /changing-the-machine-type-for-your-codespace
   - /setting-your-default-editor-for-codespaces
   - /setting-your-default-region-for-codespaces
+  - /setting-your-timeout-period-for-codespaces
   - /prebuilding-codespaces-for-your-project
 ---
 

content/codespaces/customizing-your-codespace/index.md

@@ -0,0 +1,46 @@
+---
+title: Setting your timeout period for Codespaces
+intro: 'You can set your default timeout for {% data variables.product.prodname_codespaces %} in your personal settings page.'
+product: '{% data reusables.gated-features.codespaces %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+shortTitle: Set the timeout
+---
+
+A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace.
+
+{% warning %}
+
+**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
+
+{% endwarning %}
+
+## Setting your default timeout
+
+{% include tool-switcher %}
+
+{% webui %}
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
+   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To set the timeout period, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (5 hours).
+
+```shell
+gh codespace create --idle-timeout 90m
+```
+
+If you do not specify a timeout period when creating a codespace, then your default timeout period will be used. You cannot currently specify a default timeout period for all future codespaces through {% data variables.product.prodname_cli %}.
+
+{% endcli %}

content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md

@@ -33,7 +33,7 @@ If you have unsaved changes, your editor will prompt you to save them before exi
 
 ## Codespaces timeouts
 
-If you leave your codespace running without interaction or if you exit your codespace without explicitly stopping it, the codespace will timeout after 30 minutes of inactivity and stop running. For more information, see "[Stopping a codespace](#stopping-a-codespace)."
+If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
 
 When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."