-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add support for building typings, using a different package manager, and specifying a custom build script #6
Conversation
|
||
### Assumptions | ||
|
||
Your Javascript must be in a `js` folder, similar to how Flarum core and Flarum's first-party extensions are laid out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this also be a variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably :P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't tested (is it even possible to test this?) but LGTM
Yes! You can use act -j build -s GITHUB_TOKEN=xxxxx # Replace with a PAT I turn off WiFi when it hits the Webpack build just to make sure it doesn't commit and push anywhere 🤪 |
If you've tested this, I'm happy with it. If it turns out not to work (it should work looking at the code), we can deal with it then. |
This is a breaking change.
...but I have added a backcompat layer, even though I really shouldn't have to.
I have shifted syntax to use
with
instead ofenv
, as this is designed for parameters.See README for new syntax. Core has been updated accordingly.
We really (like REALLY) should be using tags for our actions... this will break every repo this action is on.
Prerequisite of flarum/framework#2856.