wasp-bootloader Github Workflow fixes

Allows the project to be compiled through Github Actions and the results to be downloaded as an artifact.

Aug 11 '20 18:08 LatantSea

Thanks for the getting in touch however I'm afraid I can't really take this series as it is.

First and foremost the version history is not structured to make review possible. 46 commits without any descriptions of the reason for each commit is not reviewable. Take a look at the recent commits in the main wasp-os branch to get a sense of how commits should be structured to make it possible to review them.

There are a couple of other related activities taking place that you might like to be aware of.

I'm afraid I fixed the CI builds this afternoon and didn't notice this PR until after I had done so. That's my fault not yours... I overlooked the notification e-mail but nevertheless I have already pushed my fix.

Finally there are a couple of developers on the wasp-os repo working to build all the wasp-os artefacts and make them available in one place. See https://github.com/daniel-thompson/wasp-os/pull/52 and https://github.com/daniel-thompson/wasp-os/pull/53 for details and https://github.com/AlwaysLivid/wasp-os/actions/runs/196271359 if you want to see an example of the artefacts.

Aug 15 '20 18:08 daniel-thompson

@LatantSea Please reach out to us, we'd appreciate your help and I'd love to discuss some of the things regarding the PR with you.

Aug 17 '20 16:08 n0toose

Hey, thank you for your patience, I'm new to Github. I'm still very unfamiliar with the features and interface. @daniel-thompson Thank you for your response and direction. I'll try to emulate the pre-existing commit structure for future commits @AlwaysLivid On what may I assist? I'm currently working on a classic card game clone for Wasp-os while learning micropython

Aug 17 '20 19:08 LatantSea

@AlwaysLivid On what may I assist? I'm currently working on a classic card game clone for Wasp-os while learning micropython

We already have some sort of implementation under development which is meant to stay true to what the documentation describes, but there are a decent amount of technicalities that need to get done right and fixed before considering it.

If you could reach out to me privately, I'd be able to discuss what we currently "have in store" and what needs to be worked on. I believe that discussing a completely irrelevant pull request over here would seem kind of inappropriate, but both me and Mirko have been a bit busy and could probably make use of a helping hand. :D

Aug 17 '20 20:08 n0toose