novolis-governance / imports-todo/workflows-and-release-ci.md
Workflows + ReleaseOrchistrator — CI pieces (mine)
Policies that keep the org coherent
dotnetgovernancenovolis
Sources:
D:\repos\Workflows— reusable GitHub ActionsD:\repos\ReleaseOrchistrator— multi-stage release stubD:\github\frank-docfx-publish,frank-dotnet-script-*— doc/tooling (optional)
What
| Repo | Content |
|---|---|
| **Workflows** | Composite actions: dotnet restore/build/test/pack/publish patterns |
| **ReleaseOrchistrator** | dev → test → prod approval workflow skeleton |
Not platform libraries — reference by URL in novolis-workflows (GitHub org) and per-repo .github/workflows.
Why
novolis-workflowsorg templates should stay DRY; Frank Workflows repo already exists locally.- Duplicating YAML into every
novolis-*repo drifts; central reusable workflows match governance scale (22+ repos).
How
- Audit
D:\repos\Workflowsactions vsnovolis-workflowscurrent workflows. - Publish/mirror needed composites to
Novolis-Platform/.githubornovolis-workflowsrepo. - Wire
verify-nuget-only.ps1,doc-audit.ps1, anddotnet testin standard pipeline. - Evolve ReleaseOrchistrator into documented release policy (release-policy.md) — approval gates for GPR.
Skip
- Packaging Workflows as NuGet.
- Importing ReleaseOrchistrator as C# library.
Acceptance
- New
novolis-*repo created from template gets workflow viaworkflow_callnot copy-paste. - Documented in maintainer-guide.md.