Goal
Build a shared GitHub Actions platform for LibreCode/LibreSign with reproducible upstream imports, a GitHub-native organization catalog, explicit downstream adaptations, safe consumer updates and tested security controls.
Final architecture
Nextcloud / selected upstreams
↓
immutable source commit + SHA-256
↓
vendored source
↓
minimal LibreCode organization patch
↓
generated workflow template
↓
tests + actionlint + zizmor + workflow policy
↓
LibreCodeCoop/.github catalog
↓
consumer-local sync-workflow-templates.yml
↓
actions/sync-workflows
↓
optional consumer-local <workflow>.patch
↓
actions-lock.txt + reviewable PR
LibreCodeCoop/github-workflows is the source of truth.
LibreCodeCoop/.github is the catalog/distribution layer.
Consumers own product-specific patches, credentials, branch policy and the review/merge decision.
Completed workstreams
Production validation
The materialized consumer-sync model has been exercised in:
- LibreCodeCoop/extract;
- LibreCodeCoop/profile_fields;
- LibreSign/libresign.
The obsolete central consumers.json / sync-consumers.yml architecture has been removed.
Definition of done
The initial shared GitHub workflow platform roadmap is complete. Future workflow families or policy extensions should be tracked as new focused issues rather than keeping this bootstrap roadmap open.
Goal
Build a shared GitHub Actions platform for LibreCode/LibreSign with reproducible upstream imports, a GitHub-native organization catalog, explicit downstream adaptations, safe consumer updates and tested security controls.
Final architecture
LibreCodeCoop/github-workflowsis the source of truth.LibreCodeCoop/.githubis the catalog/distribution layer.Consumers own product-specific patches, credentials, branch policy and the review/merge decision.
Completed workstreams
Production validation
The materialized consumer-sync model has been exercised in:
The obsolete central
consumers.json/sync-consumers.ymlarchitecture has been removed.Definition of done
The initial shared GitHub workflow platform roadmap is complete. Future workflow families or policy extensions should be tracked as new focused issues rather than keeping this bootstrap roadmap open.