CI / CD
Path: .github/workflows/ (+ .github/labeler.yml)
The repository runs a security-and-hygiene oriented GitHub Actions suite. There is no compile-and-test pipeline yet (the unit-test projects don't build — see Project Status); what exists today:
| Workflow | File | What it does |
|---|---|---|
| Microsoft C++ Code Analysis | msvc.yml | On push/PR to main (and weekly): checks out, configures CMake on windows-latest with -DCMAKE_POLICY_VERSION_MINIMUM=3.5, runs MSVC static analysis and uploads SARIF results to GitHub code scanning |
| Semgrep | semgrep.yml | Semgrep SAST scanning on push/PR |
| OSV-Scanner | osv-scanner.yml | Scans dependencies for known vulnerabilities (OSV database) via the reusable Google action (v1.7.1) |
| Scorecard supply-chain security | scorecard.yml | OpenSSF Scorecard for supply-chain hygiene |
| Labeler | label.yml + labeler.yml | Auto-labels PRs by changed paths |
| Mark stale issues and pull requests | stale.yml | Stale bot |
| sync to codeberg | sync.yml | Mirrors the repo to Codeberg |
The ~557 "issues"
The README tracks "Fix all 557 'issues' and stuff scanned by Github" — these are findings
from the SARIF/semgrep/OSV pipelines above, visible in the repo's Security → Code scanning
tab. Triage them there; each workflow's results upload with security-events: write.
Adding a build pipeline
When the unit-test projects build again, the natural next step is a workflow that:
- Configures CMake (
-DCMAKE_POLICY_VERSION_MINIMUM=3.5— see Building with CMake) - Builds the ✅ module set
- Runs
RobloxTest/*.UnitTest.Runexecutables, publishing results as artifacts
The Base.UnitTest.Lib TeamCity integration (teamcity_messages.cpp) shows how the original
team consumed Boost.Test output from CI.
Docs deployment
A dedicated workflow builds and publishes this documentation site to GitHub Pages — configuration and usage are described in Maintaining the docs site.