feat: Add execute-workflow action #228
Conversation
janbuchar
added
adhoc
| permissions: | ||
| contents: write |
There was a problem hiding this comment.
I don't think this is needed tbh, since you'll be using the service acc token anyways
execute-workflow/package.json
Outdated
| "description": "Execute GitHub Actions workflows", | ||
| "main": "dist/index.js", | ||
| "scripts": { | ||
| "build": "ncc build src/main.ts -o dist", |
There was a problem hiding this comment.
Passing the -m (--minify) flag cuts the size in half. (~1.1MB -> 592kB)
I'm wondering, would this lead to a more compact git history, should the dependencies update from time to time? Or would the minimized file fully rebuild on each update, making larger diffs in the end?
What do you guys think? I suppose we don't care about the readability of the built code, right?
There was a problem hiding this comment.
Good call, let's do that.
Co-authored-by: Jindřich Bär <[email protected]>
Co-authored-by: Vlad Frangu <[email protected]>
Yeah, trust me I feel that. But we can have at least some type checking of the actions this way, which is nice. |
3 participants
The action was added to allow bypassing the single-workflow restriction in npm trusted publishing. It simply triggers an external workflow and waits for it to complete. See usage in apify/apify-client-js#770