Skip to main content

Restricting the retention period for codespaces

You can set a maximum retention period for any codespaces owned by your organization.

To manage retention constraints for an organization's codespaces, you must be an owner of the organization.

GitHub Codespaces is available for organizations using GitHub Team or GitHub Enterprise Cloud. 詳しい情報については「GitHubの製品」を参照してください。


Codespaces are automatically deleted after they have been stopped and have remained inactive for a defined number of days. The retention period for each codespace is set when the codespace is created and does not change.

Everyone who has access to GitHub Codespaces can configure a retention period for the codespaces they create. The initial setting for this default retention period is 30 days. Individual users can set this period within the range 0-30 days. For more information, see "Configuring automatic deletion of your codespaces."

As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see "About billing for GitHub Codespaces." You can set a maximum retention period for all, or for specific, repositories owned by your organization.

Setting organization-wide and repository-specific policies

When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a codespace retention constraint, then the retention constraints in any policies that are targeted at specific repositories should be shorter than the restriction configured for the entire organization, or they will have no effect. The shortest retention period - in an organization-wide policy, a policy targeted at specified repositories, or the default retention period in someone's personal settings - is applied.

If you add an organization-wide policy with a retention constraint, you should set the retention period to the longest acceptable period. You can then add separate policies that set the maximum retention to a shorter period for specific repositories in your organization.

Adding a policy to set a maximum codespace retention period

  1. In the top right corner of, click your profile photo, then click Your organizations. プロフィールメニューのあなたのOrganization

  2. Organizationの隣のSettings(設定)をクリックしてください。 設定ボタン

  3. サイドバーの"Code, planning, and automation(コード、計画、自動化)"のセクションで、 Codespacesを選択し、続いて Policies(ポリシー)をクリックしてください。

  4. "Codespace policies( Codespaceのポリシー)"ページで、Create Policy(ポリシーの作成)をクリックしてください。

  5. 新しいポリシーの名前を入力してください。

  6. Click Add constraint and choose Retention period.

    Add a constraint for retention periods

  7. Click to edit the constraint.

    Edit the timeout constraint

  8. Enter the maximum number of days codespaces can remain stopped before they are automatically deleted, then click Save.

    Set the retention period in days


    • A day, in this context, is a 24-hour period, beginning at the time of day when the codespace was stopped.
    • The valid range is 0-30 days.
    • Setting the period to 0 will result in codespaces being immediately deleted when they are stopped, or when they timeout due to inactivity.
  9. "Change policy target(ポリシーターゲットの変更)"のエリアで、ドロップダウンボタンをクリックしてください。

  10. All repositories(すべてのリポジトリ)もしくはSelected repositories(選択したリポジトリ)を選択し、ポリシーを適用するリポジトリを決定してください。

  11. [Selected repositories] を選択した場合、以下の手順に従います。

    1. をクリックします。


    2. ポリシーを適用したいリポジトリを選択してください。

    3. リポジトリリストの下部で、Select repositories(リポジトリの選択)をクリックしてください。


  12. If you want to add another constraint to the policy, click Add constraint and choose another constraint. For information about other constraints, see "Restricting access to machine types," "Restricting the visibility of forwarded ports," and "Restricting the idle timeout period."

  13. After you've finished adding constraints to your policy, click Save.

The policy will be applied to all new codespaces that are created.

Editing a policy

You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.

The retention period constraint is only applied to codespaces when they are created. Editing a policy has no effect on existing codespaces.

  1. Display the "Codespace policies" page. For more information, see "Adding a policy to set a maximum codespace retention period."
  2. Click the name of the policy you want to edit.
  3. Make the required changes then click Save.

Deleting a policy

You can delete a policy at any time. Deleting a policy has no effect on existing codespaces.

  1. Display the "Codespace policies" page. For more information, see "Adding a policy to set a maximum codespace retention period."

  2. Click the delete button to the right of the policy you want to delete.

    The delete button for a policy