After 30 minutes of inactivity, a GitHub Codespace will:

The correct answer is D. Time out. By default, a GitHub Codespace times out after 30 minutes of inactivity. When timed out, the codespace stops running (saving compute costs) but is not deleted - your files and changes are preserved. Option A (deleted) is incorrect; deletion only happens after an extended period…

Modern Development

Question

Options

ABe deleted
BCommit changes
CRestart
DTime out

How the community answered

(42 responses)

A
2% (1)
B
5% (2)
C
2% (1)
D
90% (38)

Explanation

By default, a GitHub Codespace times out after 30 minutes of inactivity. When timed out, the codespace stops running (saving compute costs) but is not deleted - your files and changes are preserved. Option A (deleted) is incorrect; deletion only happens after an extended period of no use (default 30 days). Options B (commit) and C (restart) do not occur automatically on timeout.

Topics

#GitHub Codespaces#Codespaces lifecycle#Inactivity timeout#Cloud development environments

Community Discussion

No community discussion yet for this question.

Full GH-900 Practice