Stop codespaces within your organization.Stop, or delete codespaces within your organization.Get information on a specific codespace within your organization.List all codespaces within your organization.With this beta, organization admins can use the following REST API and CLI commands: We are also introducing support for organization level APIs and CLI commands in public beta so that admins can programmatically manage their organization-owned codespaces at scale. With this, admins no longer need to remind individual teams to clean up stale codespaces thus minimizing wasteful resources and saving money for their organization. The organization retention policy will override the individual default retention setting for organization-owned codespaces. Organization admins will also be able to set an organization-level retention constraint for their organization’s codespaces. Retention policy for organization administrators

Additionally, developers will be notified via email and in-product messaging to help them stay informed about the auto-deletion. The retention counter for inactive codespaces can be reset by connecting to the instance. With that, developers no longer need to remember to manually clean up old instances of dev environments that may be unintentionally generating additional costs. The retention period applies to all individual users on that are using Codespaces and can be adjusted to a maximum value of 30 days. To enable auto-cleanup of unused codespaces, inactive codespaces will now be automatically deleted if they have been unused after a period of 30 days. Today, we’re releasing capabilities that will enable developers and organizations to efficiently manage and confidently scale with Codespaces.

Github actions cache