-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: make vscode extension update more generic #471
ci: make vscode extension update more generic #471
Conversation
The input to the update-vscode-extensions action can now be a default devcontainer.json file.
Quality Gate passedIssues Measures |
Compressed layer size comparisonComparing
|
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
Compressed layer size comparisonComparing
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! devcontainer.json is now consolidated!
Have you also considered using the "features" key? This may help with debloating the image
"features": { "ghcr.io/devcontainers/features/git:1": {}, "ghcr.io/devcontainers-contrib/features/ccache-asdf:2": {}, "ghcr.io/devcontainers-contrib/features/curl-apt-get:1": {}, "ghcr.io/devcontainers-contrib/features/wget-apt-get:1": {} }
Pull Request Report (#471)Static measures
Time related measures
Status check related measures
|
🎉 Hooray! The changes in this pull request went live with the release of v5.1.3 🎉 |
Pull Request
Description of changes
The input to the update-vscode-extensions action can now be a default devcontainer.json file. This enables running the update action against standard devcontainer.json files.
Checklist