Update Github Actions to automatically manage releases

thorrak / tiltbridge

Tilt Hydrometer to WiFi Bridge

http://www.tiltbridge.com/

Other

61 stars 27 forks source link

Update Github Actions to automatically manage releases #192

Closed TaplistIOTeam closed 3 years ago

TaplistIOTeam commented 3 years ago

This change will:

Create (or update) a tag and release named latest-{master,devel} every time a PR is merged to one of those branches; and
Create a new release when a tag matching v* is pushed

The former means "bleeding edge" auto-built binaries should always be available, e.g. to interested testers. The latter I hope removes a chore associated with cutting new releases: just push the tag & let the action handle the rest.

Because of the conditional nature of those triggers, we won't be able to observe either of these things in this PR, unless it is merged. So I did a fake PR & merge in our fork: here's the PR, the action that ran once merged, and the latest-devel release the action created.

thorrak commented 3 years ago

Ugh. You're going to make me build actual Github integration for TiltBridge's firmware list, aren't you?

😢

TaplistIOTeam commented 3 years ago

Hahah. That thought did cross my mind! Hit up releases api client side from the firmware page... :)

thorrak commented 3 years ago

Hahah. That thought did cross my mind! Hit up releases api client side from the firmware page... :)

Interestingly enough, my project earlier today was building basically this exact code for a different project. I will admit I was thinking of going down this route...

Project for later this year. ;)

thorrak commented 3 years ago

BTW - I'm holding off on merging this until probably ~Sunday due to the way that BrewFlasher integrates with everything. Although I don't expect that this will cause any issues, I also don't want to get excited about having automatically updating releases and stay up late working on the same.

TaplistIOTeam commented 3 years ago

Haha, no problem! Run with it however + whenever you see fit; whipped up out of pure curiosity.

TaplistIOTeam commented 3 years ago

@lbussy I notice you are still maintaining firmware manually in the cloud branch. If you're interested, you could merge this and start getting some mileage on it. Something like the following:

Merge this PR as is. (No releases get auto-created until a tag is pushed).
Within the cloud branch, or wherever active development is happening, start using tags to trigger builds. eg:
- v2.0.0-cloud-pre1

No rush, just a small idea to start getting some cycles + keep this from bit rotting.

thorrak commented 3 years ago

Man, I have the memory of a goldfish. Merging.