Managing gerber file releases for KiCad projects has always been a bit informal — manually exported, inconsistently packaged, and only loosely tied to any point in the git history. After getting to grips with GitHub Actions on a previous project, I wondered whether the same trigger-based approach could bring some proper structure to it.
Using GitHub Actions for Consistent Gerber File Releases in KiCad
Rebooting Electronics 