Repository navigation
Context View
sergio velderrain edited this page Nov 9, 2026
·
1 revision
- External actors: the fork owner (operator) dispatching workflows and
reviewing escalations; contributors opening PRs against
feature/*branches (perADR-0001's documented GitFlow model; in practice, recent work has also used more specific topic-branch names likeround6-semantic-audit-fixesfor the samefeature/*-equivalent role). - Upstream systems:
svelderrainruiz/repo-standards-review(the authoritative compliance standard this repo is assessed against); GitHub itself (Actions, Issues, Releases, Wiki). - Downstream systems: consumer repositories (e.g.
VITechnologies/SandboxSBOMReporting) that pin this engine's reusable workflows/scripts -- a release commit SHA for the one genuinelyworkflow_call-consumable workflow (toolchain-smoke-test.yml) and directly-invoked scripts, or a vendored copy forworkflow_dispatch-only workflows (see README's Consumption model); not always a tagged release specifically -- e.g.SandboxSBOMReporting's separatePROJECTBUDDY_VM_REFpins a descriptively-labeled, untagged commit SHA; self-hosted runner VMs (Windows+LabVIEW, Ubuntu+LabVIEW) this engine provisions; the NI LabVIEW/VIPM toolchain those VMs run.