Open eitsupi opened 1 year ago
Hi 👋
Trying to clarify my understanding for this issue 👀
Majority of the community uses devcontainers/action to release Features/Templates. @eitsupi are you expecting the devcontainers/action
to support this new (prerelease
) option which avoids creating a release?
The devcontainers/features repo, runs this action as soon as the PR is merged (which ends up creating a new release). However, the workflow cadence can be controlled within the workflow (like switching it to manual runs, @eitsupi wondering if that could help in the meanwhile?)
Thanks for the reply. Your understanding is correct. The only workaround now is to not execute the command to publish.
Nice, transferred to the action repo! I think this should be easily doable and helpful for folks, @joshspicer any concerns?
I assume this is a new field of devcontainer.json, so I assumed it would need to be defined in the Spec.
Ah, my bad. I assumed it to be added as a new property for the action. I can transfer again 😅
When developing new Features or Templates, we may want to include it in the default branch of the repository, but not release it yet. In such cases, it may be useful to set a status that prevents release.
Something like: