In the current implementation, the ci action is referenced with tags that pull the main repo code. As a result, the compiled JavaScript needs to exist in the repo. However, this adds a required (local) build step when making changes and increases the number of conflicting changes across PRs.
The action for publishing dev container features uses https://github.com/JasonEtco/build-and-tag-action in the publishing step.
From a quick scan, this packages a compiled version of the code under the tag. If the same approach can be used here this would allow removal of the compiled output.
Action usage here
In the current implementation, the ci action is referenced with tags that pull the main repo code. As a result, the compiled JavaScript needs to exist in the repo. However, this adds a required (local) build step when making changes and increases the number of conflicting changes across PRs.
The action for publishing dev container features uses https://github.com/JasonEtco/build-and-tag-action in the publishing step.
From a quick scan, this packages a compiled version of the code under the tag. If the same approach can be used here this would allow removal of the compiled output.
Action usage here