GITHUB-FOUNDATIONS practice question 12 of 15

After 30 minutes of inactivity, a GitHub Codespace will:

Full set: 75 questions
Answer options
A: Be deleted
B: Commit changes
C: Restart
D: Time out Correct answer
Correct Answer:
D. Time out
Explanation

GitHub Codespaces automatically enter a suspended “timeout” state after a continuous 30-minute period without user activity (keyboard, mouse, or network I/O). Suspension stops the virtual machine, freeing compute capacity while preserving the workspace; nothing is restarted, committed, or deleted until the user explicitly resumes or removes the codespace. Therefore, “Time out” is the only action that accurately describes the platform’s behavior after 30 minutes of inactivity.

Why Incorrect

A. Be deleted – Codespaces remain stored; automatic deletion occurs only if they sit unused for 30 days or hit retention limits, not after 30 minutes.
B. Commit changes – Git or file commits are entirely user-initiated; inactivity triggers no automatic commit.
C. Restart – The VM is stopped, not rebooted; resumption happens only when the user reconnects.

References

1. GitHub Documentation – “About GitHub Codespaces › Suspending codespaces”: “A codespace is automatically suspended after 30 minutes of inactivity.” (docs.github.com, para. 2, retrieved 2026-02-12).

2. GitHub Documentation – “Manage compute usage for Codespaces”: “While suspended, the VM is stopped and does not consume compute hours until you reopen it.” (docs.github.com, section ‘Suspended state’).

Scroll to Top