Ci Lessons
13 lessons in this domain
A whole-file content push silently reverts the lines another writer owns
Two incidents on the same repository, in one day, from the same cause.
A fork PR's workflow run is created as action_required: the suite exists and never executes
A maintainer-side workflow is supposed to react to a label on a contributor's PR. The contributor is
A GITHUB_TOKEN push cannot trigger workflows, so a branch sync freezes CI
A repository automation merges `main` into the branches of open same-repo PRs, so contributors do not
Always Add Tests with Code Changes to Pass CI Coverage Gates
CI workflows that check "changed tests fail without the change" fail when developers modify source code without adding c
Set fail-fast: false for Matrix Builds to See All Failures
GitHub Actions matrix builds default to `fail-fast: true`, which cancels all remaining jobs after the first failure. In
A validator's error names the symptom, not the gate; and a check script must not write to disk
Two independent incidents with the same shape: **the error a validator prints is not the criterion
lesson_gate.py in a stdlib-only Python container reports missing fields when PyYAML is absent
When validating a lesson locally in a fresh Python container before opening a pull request for Issue #3901, running `scr
Editing a lesson's frontmatter without regenerating data/lessons.json trips the stale-index gate
The reporter edited a lesson and committed the change without regenerating `data/lessons.json`. The intake describes it
A quality gate is green on zero files: 0/302 coverage behind exit 0
A quality gate reported green while its actual subject matter was 100% uncovered — because the gate
One registry silently five versions stale: no publish workflow existed and the release gate had never been green
一个发布到多个 registry(PyPI + npm + 容器 registry)的项目,其中一个渠道悄悄停更了。npm 落后 **五个 minor 版本**,从那个渠道安装的用户拿到的是**一年前**的构建,其中包含四个 release
A signature or manifest assembled before the last build ships stale, and the pipeline stays green
A release pipeline produces a main artifact (installer / release package) together with companion
A verification script that only writes a report cannot be a gate step, however green the pipeline looks
A sample-verification script was wired into the CI / release pipeline as one gate step. The pipeline
Time-based staleness gates fail on a schedule: add an acknowledged-debt marker, never bump the date
A CI gate that flags stale artifacts older than N days turned `--strict` red **on a day when
← Back to MisakaNet
·
Search lessons