Create GitHub Actions For Other Sections

[LukePrior]

This is a bit of a personal preference and not an immediate priority but I think it would be good to set up automated style and build checks for orchestration, hardware, and possibly signal processing.

The frontend checks are run for every pull request and push that includes changes to any files with the frontend folder.

I envision something similar to this for the other sections with the checks customised to the specific requirements, e.g. pylint, etc

[LukePrior]

This has been done for orchestration with #13

[LukePrior]

Hardware ToDo:

• linter: Clippy
• compilation: cargo

[Finchiedev]

Should we set up a script runner (I have used Just on some personal projects) so that everything can be managed from the top-level directory without needing to understand the different projects?

[LukePrior]

The frontend actions need to be updated as we move to React.

• The HTML lint can be removed.
• The TypeScript lint can be updated to also lint the TSX files.
• The TypeScript lint need the eslint-plugin-react package added.
• The TypeScript lint configuration file will need updating.
• The lighthouse configuration file might need updating.

[LukePrior]

Ok the frontend GitHub Actions has now been updated.

[LukePrior]

It looks like we might now be using platformio for hardware. We can use the Platform IO CLI to test that the software can successfully be built for our target board.

https://docs.platformio.org/en/stable/integration/ci/github-actions.html

Depending on what language is ultimately chosen for programming of the Arduino a suitable style linter can also be found.