Note: The ability to prebuild codespaces is currently in beta and subject to change.
Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild template. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team.
Para obtener más información, consulta la sección "Introducción a los contenedores dev".
Testing changes to the dev container configuration
-
Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "Creating a codespace ."
-
In the codespace, check out a test branch. Para obtener más información, consulta la sección "Utilizar el control de código fuente en tu codespace."
-
Make the required changes to the dev container configuration.
-
Apply the changes by rebuilding the container. Para obtener más información, consulta la sección "Introducción a los contenedores dev".
-
After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild template for that branch.
Note: Creating this codespace will take longer than usual because it will not be created from a prebuild.