Add standard devcontainer #1269
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
1 similar comment
Does the PR have any schema changes?Looking good! No breaking changes found. |
danielrbradley
force-pushed
the
danielrbradley/devcontainer
branch
from
b06cac4 to
fac042d
Compare
danielrbradley
force-pushed
the
danielrbradley/devcontainer
branch
from
fac042d to
8561986
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
1 similar comment
Does the PR have any schema changes?Looking good! No breaking changes found. |
|
Wonder if there's an easy way to keep these in sync, as I've pretty much just made a change to the pulumi/pulumi one to fix a build on the latest base image (pulumi/pulumi@f8a98b2) |
danielrbradley
added
the
impact/no-changelog-required
|
Not sure on the alternative approaches without knowing how much different projects can vary in their required setup. I guess the ideal would be to have a single image pre-built for each of Codespaces and another for Gitpod as they don't seem to be compatible, then each project points to the latest image. Would it be worth getting this in as-is if it's functional, with an aim to start a wider conversation around standard virtualized development environments? |
You can use Git submodules and reuse dev container configurations across repositories. |
Copied from
pulumi/pulumi- makes it easier to use project in Codespaces and GitPod.