While reviewing sanity-check workflows (apps, demos, kits), I noticed repeated job-level patterns such as checkout, OS setup, Python setup, and matrix configuration.
Although reusable steps are already used, the job structure itself is duplicated across workflows.
Proposed solution:
Introduce reusable workflows using workflow_call to encapsulate common job logic and reuse it across workflows.
Benefits:
- Reduces duplication at job level
- Improves maintainability
- Simplifies future updates
I can work on implementing this refactor.
While reviewing sanity-check workflows (apps, demos, kits), I noticed repeated job-level patterns such as checkout, OS setup, Python setup, and matrix configuration.
Although reusable steps are already used, the job structure itself is duplicated across workflows.
Proposed solution:
Introduce reusable workflows using workflow_call to encapsulate common job logic and reuse it across workflows.
Benefits:
I can work on implementing this refactor.