Skip to content

Conversation

@luigimak
Copy link

Replace the hardcoded device matrix with a dynamic one loaded from JSON files in configs/.
This allows easier maintenance and device onboarding without editing the workflow file.

Also adds a new workflow_dispatch input 'op_model' to selectively build a single device

This change improves scalability and user flexibility during manual workflow dispatch.

Replace the hardcoded device matrix with a dynamic one loaded from
JSON files in configs/. This allows easier maintenance and device
onboarding without editing the workflow file.

Also adds a new workflow_dispatch input 'op_model' to selectively
build a single device

This change improves scalability and user flexibility during manual
workflow dispatch.
@luigimak luigimak changed the title feat: migrate to dynamic device matrix from configs/ feat: migrate to dynamic device matrix from configs/ (test-remote-action-build) Oct 18, 2025
…parsing

This change refactors the entire kernel build pipeline to use a single
JSON configuration per device instead of
individual matrix inputs.

Key improvements:
- Workflow now passes the full matrix as op_config_json via toJSON(matrix)
- All 26 device configs updated to include "hmbird"

This enables true extensibility: new devices or config options require
only a JSON file—no changes to the workflow or action logic.
@fatalcoder524 fatalcoder524 merged commit da1e1cf into fatalcoder524:test-remote-action-build Oct 20, 2025
@luigimak luigimak deleted the test-remote-action-build_json branch October 20, 2025 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants