Remove unnecessary steps from "Compile Examples" CI workflow #9
Conversation
The arduino/actions/libraried/compile-examples action's installation of the electroniccats:mbed package via Boards Manager installs the platform's tools dependencies, so it's not necessary to do this separately.
Unlike the arduino:mbed platform, this repository contains a bundled copy of ArduinoCore-API, so there is no need for the workflow to do it.
There were two electroniccats:mbed platform dependency definitions listed in the arduino/actions/libraries/compile-examples action's platforms input. The one that specifies the package index URL is the complete one and the other is unnecessary.
|
Because I'm not familiar with this platform, I had to make some guesses about how the workflow should be configured. It's possible that some of the things I removed were put there for purposes I didn't understand, so please have a look and let me know if I've missed the mark. An optional improvement I would suggest is to switch to using the maintained version of the sketch compilation action. The |
|
Ey thanks! @per1234 , I'm going to move to https://github.com/arduino/compile-sketches in the next pullrequest |
|
You're welcome. Please let me know if you run into any problems when migrating to You also might like to take advantage of this new |
The "Compile Examples" GitHub Actions workflow contained some unnecessary steps. In addition to being not ideal from a maintenance and efficiency standpoint, the configuration was actually causing the workflow to fail.