Automatic Builds

[bakustarver]

Enable GitHub Actions autobuilds to generate release artifacts for Windows, Linux and macOS automatically.

They appear as workflow runs in the Actions tab, with downloadable builds attached.

[nathan-b]

@bakustarver thanks for the contribution!

I'm curious what the goal here is. Specifically, I'm just wondering if it would be preferable to build a real release workflow rather than ad-hoc building artifacts on every push. What do you think?

I also note that every job runs npm i -D electron-builder but then invokes npx electron-packager, which seems a bit off to me.

[bakustarver]

I replaced push-triggered artifact creation with a workflow_dispatch event.
During testing, I had added npm i -D electron-builder. it’s now removed.

If needed, I can also configure a separate workflow to automatically publish builds to the release tab.

[bakustarver]

I added another workflow that handles publishing artifacts in the Release tab.

[nathan-b]

Thanks for the fix! I think what I'd like to see when it comes to releases is a tag-based triggered release. If I push a v*.*.* tag then the automation can pick it up and use ${{ github.ref_name }} as the version (so the version is set by whoever pushes the tag), or at minimum read from package.json. The run_number scheme will produce confusing release history.

I did something similar in another one of my projects that you're welcome to cheat off of here if you'd like :)

[bakustarver]

My goal is to get an automatic build without npm.
I think you can polish the workflow file further on your own.