Why Codespaces storage usage warning? #39615
Select Topic AreaQuestion BodyHey! A few days ago, I have received an email warning me I had used 75% of included services for GitHub Codespaces Storage. |
Replies: 14 comments 18 replies
|
Hi there @Kebap and welcome to our community! Thank you for asking a great question 🙂 To get started, introduce yourself in our official introduction thread |
|
I am getting the same warning. Started last week. Both emails and now a message in VSCode itself that says... "You've used 90% of included services for GitHub Codespaces Storage. To continue using Codespaces uninterrupted, update your spending limit." The repo I am editing in Codespaces is 13KB zipped when downloaded from GitHub. Here is the link. Strange that there are no links or prompts to see how much space I have left or how I have used so much space? Just a link to pay for more space. Nowhere does Codespace show storage space usage. Please advise as to how this can be investigated or this error fixed. Thank you. |
|
Same issue here. I do not use GitHub Codespaces, so why am I getting emails claiming "You've used 90% of included services"? |
|
I just ran into this issue, and based on this conversation in this thread, it seems this recently rolled out and it's buggy as hell. For one thing, old Codespaces are calculated as accumulating storage every single day, even if you just have one of them and never use it. So one old Codespace at 30 days a month is like saying you have 30 repos using Codespaces a month. It chews through the usage limit incredibly quickly. Here's what to do:
|
|
i am using codespaces but storage is only 32 gb :( |
|
So, after digging around a little I can safely say that the warning I'm getting is from prebuild storage. From the screenshots I've seen from other people this also seems to be the case for them. Please GitHub, make your goddamn emails more clear about what you actually mean. |
See my answer above. Prebuild storage is basically the stuff you generate on builds with actions. Try auto-removing some of that! |
|
I'm so close to close my github account because of that, those dudes are blind, or idiot ? |
|
This can happen because codespaces use storage even when you aren't actively using. Check metered usage settings |
|
Interessante |
|
Ok I was able to find which repos were doing that through gh cli. Couldn't find them via github's frontend. Here's bash script. Have #!/usr/bin/env bash
set -uo pipefail
command -v gh >/dev/null || { echo "gh is required"; exit 1; }
gh auth status >/dev/null 2>&1 || { echo "run: gh auth login"; exit 1; }
ME=$(gh api /user -q .login)
echo "account: $ME"
echo
echo "== billing: every codespaces SKUs, quantity =="
gh api "/users/$ME/settings/billing/usage" \
--jq '.usageItems[] | select(.product=="codespaces") | "\(.date[0:7]) \(.sku) \(.quantity)"'
echo
echo "== codespaces that still exist =="
gh codespace list --limit 100 || true
echo
echo "== repos with a prebuild config =="
gh api -X GET /search/code -f "q=filename:devcontainer.json user:$ME" \
--jq '.items[].repository.full_name' 2>/dev/null | sort -u |
while read -r r; do
gh workflow list -R "$r" 2>/dev/null | grep -qi prebuild && echo "$r"
doneIt will output something like this: account: hugmouse
== billing: codespaces SKUs, quantity ==
2026-02 Codespaces compute 2-core 4.73009
2026-02 Codespaces compute 8-core 0.63603
2026-02 Codespaces prebuild storage 7.939131326
2026-02 Codespaces storage 0.378277327
2026-03 Codespaces compute 2-core 0.29789
2026-03 Codespaces prebuild storage 14.665550297
2026-03 Codespaces storage 0.334466085
2026-04 Codespaces compute 2-core 1.09609
2026-04 Codespaces prebuild storage 14.510251098
2026-04 Codespaces storage 0.101495822
2026-05 Codespaces prebuild storage 15.000014309
2026-06 Codespaces prebuild storage 15.005227268
2026-07 Codespaces prebuild storage 15.000011207
2026-08 Codespaces prebuild storage 15.000011207
2026-09 Codespaces prebuild storage 15.000009143
== codespaces that still exist ==
no codespaces found
== repos with a prebuild config ==
hugmouse/dicks
hugmouse/balls |










I just ran into this issue, and based on this conversation in this thread, it seems this recently rolled out and it's buggy as hell. For one thing, old Codespaces are calculated as accumulating storage every single day, even if you just have one of them and never use it. So one old Codespace at 30 days a month is like saying you have 30 repos using Codespaces a month. It chews through the usage limit incredibly quickly.
Here's what to do: