action icon indicating copy to clipboard operation
action copied to clipboard

GitHub Action to build & publish your own dev container assets

Results 28 action issues
Sort by recently updated
recently updated
newest added

Is there any timeline for an update to Node 20 as Node 16 is out of support since September 11th? https://nodejs.org/en/blog/announcements/nodejs16-eol Thanks

For example, I noticed there're two jsonc related dependencies: https://github.com/devcontainers/action/blob/a1930bf7eb60408bbfd6e201d88e33cdec41a25e/package.json#L34 https://github.com/devcontainers/action/blob/a1930bf7eb60408bbfd6e201d88e33cdec41a25e/package.json#L46 The one in the devDependencies was published 5 years ago, and maintained by 1 developer. I know it's not...

https://github.com/devcontainers/cli/blob/2a6ab1ac82f4917654205e2a9b1ac928260d902e/.devcontainer/devcontainer.json#L15 I know this is `devcontainer.json`, but yes the `devcontainer-feature.json` also supports this.

So we can use it everywhere not only in the GitHub Actions :) A simple PoC here: https://github.com/hellodword/action/tree/patch-3 Try it with: ```sh npx ts-node ./src/cli/main.ts features docs --owner ohhh --repo...

enhancement

## Summary We're building a devcontainer feature that includes a `dependsOn` another feature. This is causing failures using `@devcontainers/action` but seems to work with the devcontainers CLI. The documentation says...

Hi, for using this in a GitHub enterprise context it would be necessary to get the base url from the context instead of hardcoding it to github.com https://github.com/devcontainers/action/blob/5002ae5962899e0fd372f7affde2c3e176372682/src/generateDocs.ts#L120 I think...

enhancement

hello! 👋 problem: what if a company, org, or institution theoretically wants to do this: ![image](https://github.com/devcontainers/action/assets/61068799/d837592e-9b85-4ff0-ac67-32e710e2fde8) (this is THEORETICAL and i haven't actually encountered this) but only for the docs...

Just like we generate documentation for each Feature, auto-generate the repo-level README with pointers to the individual README docs.

enhancement

ref: https://github.com/devcontainers/spec/issues/178 This makes it difficult to use the test commands for folks that would like to developer features in a one-per-repo kind of manner

idk if this is the right spot to bring this up but hey 🤷‍♀️ I've recently found immense usefulness in being able to list which features changed and default to...