jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 03:44:00 -05:00
Code Issues Projects Releases Wiki Activity

Add inactivity definition (#46609)

Browse Source
This commit is contained in:
hubwriter
2023-11-28 14:47:45 +00:00
committed by GitHub
parent 388be11f52
commit 6663f0480a
3 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md
View File

@@ -22,6 +22,10 @@ A codespace will stop running after a period of inactivity. By default this peri
{% endwarning %} {% endwarning %}
### Inactivity defined
{% data reusables.codespaces.inactivity-definition %}
### Timeout periods for organization-owned repositories ### Timeout periods for organization-owned repositories
Organizations can set a maximum idle timeout policy for codespaces created from some or all of their repositories. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting. You will be notified of this after the codespace is created. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." Organizations can set a maximum idle timeout policy for codespaces created from some or all of their repositories. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting. You will be notified of this after the codespace is created. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."

6
content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
View File

@@ -28,9 +28,13 @@ As an organization owner, you may want to configure constraints on the maximum i
For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
### Inactivity defined
{% data reusables.codespaces.inactivity-definition %}
### Behavior when you set a maximum idle timeout constraint ### Behavior when you set a maximum idle timeout constraint
If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository that has a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed:
> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. > Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy.

1
data/reusables/codespaces/inactivity-definition.md Normal file
View File

@@ -0,0 +1 @@
In the context of the {% data variables.product.prodname_codespaces %} idle timeout, inactivity is defined as the absence of activity indicative of a user's presence. Personal interaction with a codespace, such as typing or using the mouse, resets the idle timeout period. Terminal activity, either input or output, also resets the idle timeout period. For example, if you publish a web app on a port from a codespace and page requests generate output in a terminal on the codespace, then each time terminal output occurs the timeout will be reset. However, if you share a port, and then don't interact with the codespace, and no terminal output is generated, the codespace will time out after the configured period.