refactor: switch to single config file and deno.json again #103
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.
Given what's mentioned by @crowlKats in #101 (comment), I thought perhaps it's better to combine
deno.json
+package.json
into onlydeno.json
once more. Given that all metadata for the action comes fromaction.yml
.The
version
field indeno.json
can instead be used if it's preferable to have PR's (e.g. #102) when new versions are released. The only field that has no equivalent indeno.json
is theauthor
field, though I don't think there's any purpose to it when this field exists inaction.yml
.