New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run action without docker #358
Comments
Yup. We can use https://github.com/probot/actions-adapter to make that happen. |
That might be a quick fix. I was thinking we would have two entry points to handle both probot and actions code. |
I tested out the two approaches mentioned in the probot-actions-adapter readme. Vendor node_modules which add nearly 1.810.297 additions Not sure either one is better. See |
Hmm not sure why, vendoring seems incomplete: https://github.com/casz/test-release-drafter-action-adapter/runs/380278004 This is testing with node_modules vendoring which seems to fail. |
Ah we cannot use yarn to for vendoring our node_modules. So the question becomes to we want to switch to npm and package-lock.json or use |
Hmm @TimonVS @toolmantim I been thinking about converting the project to typescript. Add lerna to manage release-drafter/core, release-drafter/action, release-drafter/probot Using https://github.com/actions/typescript-action as a base for release-drafter/action As to those using release-drafter/probot be it GitHub enterprise or not can continue using it. |
That sounds like a solid idea @Casz! Also really like the idea of |
I'd be excited to see this. I've been writing pure js actions and compiling with ncc. Love how fast they start and run! |
We already have a PR with ncc #376 |
I'd like to drop the need for running the action inside a docker container.
Originally posted by @Casz in #335 (comment)
The text was updated successfully, but these errors were encountered: