title | allowTitleToDifferFromFilename | intro | versions | type | topics | shortTitle | redirect_from | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Troubleshooting personalization options for GitHub Codespaces |
true |
Troubleshooting steps for common issues with dotfiles and Settings Sync. |
|
reference |
|
Personalization |
|
You can personalize {% data variables.product.prodname_github_codespaces %} by using a dotfiles
repository on {% data variables.product.product_name %} or by using Settings Sync. For more information, see "AUTOTITLE."
If your codespace fails to pick up configuration settings from dotfiles, you should work through the following debugging steps.
-
Enable dotfiles by selecting Automatically install dotfiles in your personal {% data variables.product.prodname_github_codespaces %} settings.
-
Check
/workspaces/.codespaces/.persistedshare/dotfiles
to see if your dotfiles were cloned.- If your dotfiles were cloned, try manually re-running your install script to verify that it is executable.
- If your dotfiles were not cloned, check
/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt
to see if there was a problem cloning them.
-
Check
/workspaces/.codespaces/.persistedshare/creation.log
for possible issues. For more information, see Creation logs.
If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the $CODESPACES
environment variable to add conditional logic for codespace-specific configuration settings. For more information about configuration that may be incompatible with codespaces, see:
{% data reusables.codespaces.disabling-settings-sync %}