If your codespace fails to pick up configuration settings from dotfiles, you should work through the following debugging steps.
- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use Codespace secrets instead of private dotfiles.
/workspaces/.codespaces/.persistedshare/dotfilesto 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.txtto see if there was a problem cloning them.
/workspaces/.codespaces/.persistedshare/creation.logfor 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.