Customizing Individual GitHub Codespaces
Short answer
CDE You can customize the name, default editor, and shell for an individual GitHub Codespace.
Question
Key Takeaways
The question tests the distinction between global/repository configurations and local codespace preferences, specifically highlighting that editors and shells are customizable at the instance level.
This page explains how to customize an individual GitHub Codespace by setting its name, default editor, and shell. It clarifies that repository-level policies like branch protections are not per-codespace settings.
Common mistake: Learners often incorrectly select 'branch protections' (B) because they confuse repository-level security policies with the customizable environment of a single codespace instance.
Expert Analysis
Why the Answer Is Correct
According to GitHub documentation, you can personalize your development environment for each session. You can assign a specific name (C) to identify the codespace, choose the default editor (D) such as VS Code Web or Desktop, and configure the shell (E) (e.g., bash, zsh, fish). These settings allow for a tailored experience per instance.
Why the Other Options Are Wrong
Branch protections (B) are repository-level settings defined in the repository's Branch Protection Rules. They apply to all pushes and merges within the repository and cannot be customized on a per-codespace basis. The operating system (A) is determined by the Codespace template selected during creation; while you can change templates, you do not customize the OS kernel or distribution directly within the running codespace settings.
Community Comment Notes
As Kiwi28 noted, the correct answers are C, D, and E. The community consensus confirms that naming, editor choice, and shell selection are the standard customization options available in the codespace UI and configuration files.
Exam Strategy
Always distinguish between repository-wide policies (like protection rules) and instance-specific configurations (like editors or shells) when answering GitHub exam questions.
Frequently Asked Questions
Can I change the OS of a running Codespace?
Why is branch protection not customizable?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Kiwi28 👍 1The correct answers are C, D, and E. ✅ GitHub’s official Codespaces documentation confirms that you can customize: - C. name ✅ — you can rename an individual codespace. GitHub Docs - D. default editor ✅ — you can choose whether Codespaces opens in VS Code web, VS Code desktop, or JupyterLab. GitHub Docs - E. shell ✅ — you can change the shell used in a codespace. GitHub Docs Why not the others: - A. operating system ❌ — Codespaces uses a Linux-based environment; you can change the container image/configuration, but you do not choose Windows or macOS as the codespace OS in the normal sense. - B. branch protections ❌ — branch protection is a repository setting, not a per-codespace customization.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.