Closed thisiskeithb closed 1 year ago
I like that we have access to update the boards list now, but I'm still thinking this could be automated. Perhaps pulling a copy of upstream boards.h
and parsing it on deployment?
I'll have to get this building locally and see what can be scripted through GitHub Actions.
I like that we have access to update the boards list now, but I'm still thinking this could be automated.
Automation is certainly possible, but I haven't gotten around to it with all the other junk I need to attend to. My strategy meanwhile is to occasionally look at the commit history of boards.h
in reverse chronological order and add boards until I reach the last one that was already added.
My strategy meanwhile is to occasionally look at the commit history of
boards.h
in reverse chronological order and add boards until I reach the last one that was already added.
As someone who frequently adds boards & deals with pins files a lot, I don’t have a problem with submitting PRs like I’ve done here & in https://github.com/MarlinFirmware/MarlinDocumentation/pull/514.
You don't need to go to so much trouble. This is something I will do in the general course and certainly at the time of any tagged release.
Add latest boards.