COVERAGE.md: measured baseline on master after the umount merge #2
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/turnkey-chroot!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/coverage-master"
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?
Problem: COVERAGE.md still described master as 44 percent with 10 tests.
Diagnosis: fix/umount-in-lxc merged in pull request #1 (merge commit
0b1c044) and brought chroot/init.py to 100 percent with 40 tests.Fix: a "measured baseline on master" section at the top with the new number, date and merge commit; the earlier sections are kept as the record before the merge. The threshold in .github/workflows/tests.yml stays at 95 (never lowered, and 95 is the bar for project-authored code).
Tests: none needed, documentation only; the required check runs on the merge ref as usual.
Serves BRIEF section 10 (conventions: coverage numbers are recorded where they are enforced).