Codespaces prebuilds reach general availability

GitHub has announced that Codespaces prebuilds are now generally available. Prebuilt codespaces provide a ready-to-use template with source code, editor extensions, dependencies, commands, and configurations already installed, eliminating the wait time normally associated with creating a new codespace. This is particularly beneficial for large or complex repositories, where setup can otherwise be time-consuming.

The feature entered public beta earlier this year, and GitHub has incorporated user feedback into the GA release, adding several new management and monitoring capabilities.

Controlling prebuild refresh frequency

Repository administrators now have three options for triggering prebuild configuration updates:

  • Every push (default): Prebuilds refresh on each push to the branch, ensuring new Codespaces always include the latest code and dependency changes.
  • On configuration change: Prebuilds update only when configuration files change, reducing the frequency of the Actions workflow that generates the template and thereby conserving Actions minutes.
  • Scheduled: Admins can define a custom schedule for prebuild updates, offering the greatest control over Actions usage.

These options allow admins to balance environment freshness against Actions consumption. For example, a large organization might choose hourly updates rather than per-push updates to minimize cost.

GitHub also highlighted a customer case: Vanta, a security compliance company, used prebuilds to cut developer onboarding time from two days to one minute. Vanta’s engineering team doubled in size recently, and prebuilt environments remain stable and ephemeral rather than diverging over time.

Failure alerts and configuration controls

Prebuild workflows can now notify designated individuals or teams via email when they fail. This eliminates the need for manual monitoring, allowing those responsible for managing prebuilds to address issues quickly. Admins can also disable a prebuild configuration temporarily when they need to pause updates while fixing an underlying problem.

For investigating failures, GitHub has added a setting to pause a prebuild configuration while an issue is being resolved.

Prebuild readiness indicators

The Codespaces UI now includes two labels for machine types: “prebuild ready” and a new “prebuild in progress” label. The latter appears when prebuild template creation for a branch is still underway, helping developers identify which machine types are available for immediate creation.

Billing and storage retention

With general availability, organizations are billed for the Actions minutes consumed by prebuild workflows and for the storage of prebuild templates associated with each configuration. Usage reports are available for download to track these costs per repository and region.

To manage storage costs, repository admins can configure how many prebuild template versions to retain. The default retention is two—the latest and one previous version—which helps limit storage overhead by removing older, unused templates.

Availability and getting started

Prebuilds are available on GitHub Enterprise Cloud and GitHub Team plans. Organization and repository admins can create prebuild configurations under the “Codespaces” tab in repository settings. Developers can create codespaces from a prebuild-enabled branch by selecting a machine type displaying the “prebuild ready” label.

GitHub plans to continue developing prebuild functionality for monorepos and multi-repository scenarios, with feedback collected via the GitHub Discussions forum.