A change that ships needs a changelog entry #7
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/.github!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/require-changelog"
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?
Today the Instance menu and the console mark were merged into confconsole with no entry in
debian/changelog. The code was on master, the gate was green, and the newest installable confconsole stayed2.2.3+keel1, so neither change reached an appliance. The forum image was then read as proof the menu had never been written. Nothing in the process could have noticed: a coverage gate measures the code, not whether the code can be installed.require-changelog.ymlis the missing check. A pull request that changes a file the package ships must also add a changelog entry with a greater version. Tests, documentation and CI ship nothing and are exempt, and a repository with no changelog requires nothing.The rule is
bin/require-changelog, a script with a bats suite, rather than shell inside the workflow (decision 0004). This repository therefore gains a second gate of its own,tests / coverage, besideactionlint: the tools here run inside every other repository's gate, so they are tested where they live.Test plan
tests/coverage.sh:bin/require-changelog51 of 51 lines, total 100.tests / coveragerequired here too, then callers added to the packaged repositories (confconsole, inithooks, keel, keel-transition).