For documentation checking purposes I am creating collection of End to End tasks which will follow the descriptions/instructions from thinedge documentation.
These tasks are running on an Raspberry PI.
The idea behind is that as soon as some task fail that would mean that changes in the documentations are needed or some regression mailfunction has been detected.
Types of changes
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Proposed changes
For documentation checking purposes I am creating collection of End to End tasks which will follow the descriptions/instructions from thinedge documentation. These tasks are running on an Raspberry PI. The idea behind is that as soon as some task fail that would mean that changes in the documentations are needed or some regression mailfunction has been detected.
Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments