Currently, each zmk_config repository that a user creates, includes its own Github actions pipeline definition.
As described in this document, the job definition could be imported from a global place, instead of copying it each time. Thus, it would remain up to date and would not have to be adjusted manually (e.g. for things like these). It looks like these job definitions are always the same, and if not, the imported job can be extended.
If this suggestion makes sense to you, I can create a pull request for this functionality.
Currently, each zmk_config repository that a user creates, includes its own Github actions pipeline definition.
As described in this document, the job definition could be imported from a global place, instead of copying it each time. Thus, it would remain up to date and would not have to be adjusted manually (e.g. for things like these). It looks like these job definitions are always the same, and if not, the imported job can be extended.
If this suggestion makes sense to you, I can create a pull request for this functionality.