docs/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md

title, shortTitle, allowTitleToDifferFromFilename, intro, versions, type, topics, permissions

title	shortTitle	allowTitleToDifferFromFilename	intro	versions	type	topics	permissions
Testing dev container configuration changes on a prebuild-enabled branch	Test dev container changes	true	When you change the dev container configuration for a branch that's enabled for prebuilds, you should test your changes in a codespace.	fpt ghec * *	how_to	Codespaces Set up	People with write permissions to a repository can create or edit the dev container configuration for a branch.

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. 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.

For more information, see AUTOTITLE.

Testing changes to the dev container configuration

1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see AUTOTITLE.

2. In the codespace, check out a test branch. For more information, see AUTOTITLE.

3. Make the required changes to the dev container configuration.

4. Apply the changes by rebuilding the container. For more information, see AUTOTITLE.

5. 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 for that branch.

   Note

   Creating this codespace will take longer than usual because it will not be created from a prebuild.