Codespaces Prebuild Not Working: "Prebuild Ready" Label Missing

How to fix it

Try these in order — the most common fix is first.

1. 1. Check configuration

   Copy steps
   1. Confirm a prebuild configuration exists for the branch and region
   2. Wait for the prebuild workflow run from the latest push
   3. In the Actions tab open the Codespaces Prebuilds workflow and check recent runs
   Did this fix it? Yes No

2. 2. Fix failing runs

   Copy steps
   1. Raise the GitHub Actions spending limit
   2. Edit the prebuild configuration and click Update; authorize requested permissions
   3. Temporarily disable the configuration if runs keep failing
   Did this fix it? Yes No

3. 3. Out-of-date prebuilds

   1. Admins can enable Disable prebuild optimization under advanced options in Settings > Codespaces
   Did this fix it? Yes No

Symptoms

No "Prebuild ready" label, resources not accessible in prebuild codespaces, or failed prebuild workflow runs.

Why it happens

• Dev container configuration change pushed to the prebuild branch
• Branch devcontainer config differs from its base branch
• Actions minutes used up and spending limit reached
• Repository permissions requested by devcontainer.json not authorized

This guide also covers

• codespaces prebuild not working
• codespaces prebuild ready missing
• codespaces prebuild failed

Other GitHub Codespaces errors

• Codespace Running in Recovery Mode: "This codespace is currently running in recovery mode due to a container error"
• GitHub Codespaces Creation Failed
• Can't Create a Codespace: No Option to Create on the Repository
• GitHub Codespaces "503 Service Unavailable" Error
• Codespaces "Oh no, it looks like you are offline" and Other Connection Errors
• GitHub Codespaces Port Forwarding Not Working
• Codespace Out of Storage: How to Free Disk Space
• Codespaces Included Usage Used Up: Core Hours and Storage Quota