Synchronize .devcontainer between pretext new and the pretext-codespace repository

[oscarlevin]

We currently have two main ways that an author can start a pretext project.

1. They can create a repository from the pretext-codespace repository.
2. They can run pretext new locally (or pretext init --refresh on a previously created project).

For both of these, the user gets a .devcontainer folder that let's them use codespaces. We should try to keep these containers identical. But that's tricky because part of creating a project from the template repository should be removing the directions to create the repository after it is made. Currently that is accomplished by calling pretext new -d . as part of that .devcontainer. But that recreates the .devcontainer and prompts the user to rebuild.

Any ideas are very welcome. @StevenClontz, @bjones1 ?

[bjones1]

How about only overwriting the devcontainer.json file if it's different during pretext new -d?

[StevenClontz]

My pitch: as part of the deploy-* actions (besides nightly) we create a fresh pretext new document that's pushed to pretext-codespaces. So no human ever maintains that repo - we just update it automatically as part of our release process for CLI.

[oscarlevin]

This is now implemented, and the docker image is being rebuild on each release as well.

[bjones1]

Nice!