Add Github Action workflow for build extensions

Scope

Other

Explanation

What would be cool if you could build your extension to a file so you can put it in your panel using github actions, would this be possible? like a blueprintFramework/action that builds blueprint extensions to .extension to use in a panel.

Is there an existing issue for this?

• [x] I have searched the existing issues before opening this issue.

I'm honestly all for this! Will definitely look into!

Awesome because it would be useful build extensions for example if your creating a panel for a company then you could build the extension and then install it but it's a bit complex to do a github action for it, it's possible but it involves docker images and I also not aware if there is a $IS_Developer env or something similar to make it possible.

Correct me if I understood you wrong but you'd like to build/export an extension to a <identifier>.blueprint file through a GitHub action, right?

Correct me if I understood you wrong but you'd like to build/export an extension to a <identifier>.blueprint file through a GitHub action, right?

Well I want to export the extension to a dist or out folder that contains <identifier>.blueprint file.

Scope

Other

Explanation

What would be cool if you could build your extension to a file so you can put it in your panel using github actions, would this be possible? like a blueprintFramework/action that builds blueprint extensions to .extension to use in a panel.

Is there an existing issue for this?

* [x]  I have searched the existing issues before opening this issue.

This is LIFE CHANGER for me (in windows), bcs i dont need to enter wsl then go into the directory then put the command and then test it.

UPDATE: I have gotten contact with @prplwtf on discord and provided an example action, but I am wanting to help if needed since I know github actions very well.