-
Notifications
You must be signed in to change notification settings - Fork 228
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
Distribution proposal. #40
Conversation
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.
Thanks so much for writing this up, @edgonmsft!
Co-authored-by: Brigit Murtaugh <[email protected]>
|
||
## Releases | ||
|
||
As a distribution and storage mechanism, we propose using GitHub releases. The releases would contain compressed files with the source code of the feature or template. Included with the release the corresponding metadata file would be either **devcontainer-feature.json**, **devcontainer-template.json** or **devcontainer-collection.json**. |
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.
We've decided to have a single devcontainer-collection.json
file that contains top level attributes for features
and templates
.
We should note, this file will be auto-generated from the contents in the repo (from the devcontainers/action
GitHub action, or other spec-compliant tooling)
closing in favor of #66 |
Supersedes #15