I spent the last 2 days getting github actions to build Mac, Linux and Windows builds of my never to be seen prototypes. Total waste of time, but a lot of fun.

@grumpygamer

one can immediately tell from my commit history when I work on my CI workflows

- add new CI build workflow for mac
- fix build error in new CI build workflow for mac
- adjust fix for mac CI
- trying another way?
- fix
- fix #2
- fix #3
- please work?
- why
- i am going to quit programming and go raise sheep
@gloriouscow @grumpygamer Is this all not even testable locally? Some of my over simple CI I can test run with act before I waste even more time getting it running on GitHub

@gullevek @grumpygamer

is it? maybe? probably - I dunno!

it's always fun trying to go back and figure out like which sixteen different packages did i actually have to install on in this ubuntu vm to get my project to compile because i honestly do not remember

@gloriouscow @gullevek @grumpygamer I was using nektos' act for this, worked really well for me (for linux builders) https://github.com/nektos/act otherwise the fix-commit-wait-fail cycle was too obnoxious.
@gullevek @gloriouscow I build Mac builds locally for testing/debugging, then when I want a release, I build on CI so it's consistent for all platforms.
@gullevek @gloriouscow @grumpygamer nope, you might not have the infrastructure locally to run the things, and you definitely aren't doing the weird diff handling GitHub uses where it loses all knowledge of branches and history