I'm not sure when we want to resolve #7 and make the repository publicly accessible, but when we do I'd like to activate CI for this project. I just rebased the wasm branch onto master and found the GPIO crate had accidentally been broken when we were playing around with the Device code.
If we activate CI it'll make sure master can't accidentally get broken, plus we can do nice things like generate API docs for the current code, or render our book so it can be viewed using GitHub Pages instead of needing to run mdbook serve locally.
Looked through #7 and the forum thread again, and I have no further issues, that is the decision for when to go public is yours. Do you have any more requirements/issues towards this? MVP, Readme, etc?
I'm not sure when we want to resolve #7 and make the repository publicly accessible, but when we do I'd like to activate CI for this project. I just rebased the
wasm
branch ontomaster
and found the GPIO crate had accidentally been broken when we were playing around with theDevice
code.If we activate CI it'll make sure
master
can't accidentally get broken, plus we can do nice things like generate API docs for the current code, or render our book so it can be viewed using GitHub Pages instead of needing to runmdbook serve
locally.