docs: document the CI pipeline (task order #3) #7
Reference in New Issue
Block a user
Delete Branch "docs/ci-pipeline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Document the CI pipeline that landed in PR #6 — new file
docs/ci.mdoncoreci/nova-platform. It states what the three legs gate, what a loudfailure means, and the local equivalent (
bash scripts/run_ci.sh).No product behaviour changes, no code touched.
Why
The workflow exists but nothing in the repository points a reader at it.
The next person to touch this line should not have to read the workflow
YAML to learn that a green pipeline and a green local run mean the same
thing. This also gives the line its first post-merge push event on a
branch, which is what fires the first run of the newly registered
workflow.
How to review
Read
docs/ci.mdonly — one file, no code. Check that the three legsmatch
scripts/run_ci.shand.gitea/workflows/ci.yml.Done looks like: the leg names and the failure contract match the
workflow, and the README-style structure holds (verdict first, then
what/why/action/details).
Risk
Low. Documentation only, no code and no contract changes. Blast radius:
none at runtime.
Evidence
2822f14d).coreci/nova-platform#3.
Pull request closed