Context
The TestBuild.yml / BuildRelease.yml pipeline (Blender extension validate + build, artifact/release naming) is currently duplicated byte-for-byte across simple_collider, simple_camera_manager, simple_export, simple_pbr_layering, simple_renaming, simple_toolkit, and blender-tools (partially). There's no actual link between the copies — every fix or naming change has to be manually re-applied to each repo's workflow files.
Task
Investigate consolidating this into a GitHub Actions reusable workflow (workflow_call), so there's one canonical pipeline definition and each addon repo's workflow file becomes a short wrapper passing repo-specific inputs (e.g. product name for release notes).
Things to figure out:
- Where the canonical reusable workflow should live (a dedicated repo, or hosted in one of the existing addon repos).
- Which per-repo differences need to stay as inputs (currently just
--product-name for BuildRelease.yml; checkout/cache action versions and the --repo flag are inconsistent across repos right now too and should be reconciled).
- Migration plan for each of the 7 addon repos.
Context
The TestBuild.yml / BuildRelease.yml pipeline (Blender extension validate + build, artifact/release naming) is currently duplicated byte-for-byte across simple_collider, simple_camera_manager, simple_export, simple_pbr_layering, simple_renaming, simple_toolkit, and blender-tools (partially). There's no actual link between the copies — every fix or naming change has to be manually re-applied to each repo's workflow files.
Task
Investigate consolidating this into a GitHub Actions reusable workflow (
workflow_call), so there's one canonical pipeline definition and each addon repo's workflow file becomes a short wrapper passing repo-specific inputs (e.g. product name for release notes).Things to figure out:
--product-namefor BuildRelease.yml; checkout/cache action versions and the--repoflag are inconsistent across repos right now too and should be reconciled).