-
Notifications
You must be signed in to change notification settings - Fork 15
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
GitHub action should better support a one-per-repo publishing technique #134
Comments
does something like this fit with the usecase? https://github.com/devcontainers-community/publish-feature this is what I've been using to publish features like https://github.com/orgs/devcontainers-community/repositories?q=features-&type=source&language=&sort= 👈 those each from an individual repo and then update the actual feature index collection https://github.com/devcontainers-community/features with https://github.com/devcontainers-community/update-collection am I understanding the original issue and the ref'ed issues goals and usecase is the same as my own? |
ref: devcontainers/spec#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
The text was updated successfully, but these errors were encountered: