add optional build output directory #51
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
needed out path as it can be configured differently
document new input
|
I'm fairly certain that this would be covered by #29, but I'm not sure when I might get a chance to finish that PR up. Ideally, this action would be able to inherit the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a suggestion to enable the inputs.out definition as this action currently does not allow usage of the astro config outDir.
If outDir is different than './dist' then users can specify it in the out input.
I was hesitant to call it differently like outDir our out-dir to avoid any naming case convention conflict.
The only catch is that if path is specified, then out must necessarily also be specified, which is mentioned in the description