Closed memark closed 2 months ago
Ah, you'll have to compile the typescript source into a compiled JS artifact in dist/
. This is an unfortunate but standard workflow for GitHub Actions, since the action runners can only run JS, not TS.
Run npm run build
and commit & push the changes it made, and this should pass CI.
Thanks for digging into this, I appreciate it! If you'd be open to making another PR, I'd also love a ## Contributing
section in the README (or a separate CONTRIBUTING.md
file) that describes the steps you had to take, since in retrospect they are not obvious.
Ah, got it. Makes sense.
Thanks for the explanation. I'll look into creating a small file for contributing. (I do think it should be separate, given that the README is what also shows up at the Github actions marketplace.)
I do think it should be separate, given that the README is what also shows up at the Github actions marketplace.
Good call! I forgot about the marketplace preview.
When typechecking (
npx tsc -b
) the project locally, an error is reportedThis is fixed in newer versions of
path-scurry
, which we pull in viaglob
.Updating
glob
solves the issue.