A project's own checks join the shared ones
A project's own guidelines may add checks, listed in a rule of theirs refining this one with what each checks and what a failure costs. Each counts among the checks of §s-jau82aq9juv9zzh: it is held to all that rule says of a check, runs wherever they run, and refuses unless that list says it reports.
A project's own kinds of node and fields carry requirements no check of the SpecSheriff guidelines knows. Run where the shared checks run and held to what they are held to, a project's check holds every participant as they do, rather than resting on whoever remembers to run it. Listed in one rule, the project's part of whether a commit goes through stands in one place, and what a failure costs is confirmed by the specification's owner (§s-67vekyup7y8smap).
The links it makes
The links made to it
- cites ← What is checked, when, and what a failure costs
- cites ← A project's own checks and generators are tested against the rule listing them
- cites ← At a commit and at a push, the project's own tools run after the SpecSheriff tools
- cites ← Where the files are
- implements ← The commands
- implements ← How a project's own check is run
The decisions taken on it
- Problem
A project's own rules carried requirements no check of SpecSheriff knew, and a check of its own had no place to run.
- Ruling
The owner: a project's own checks run with the shared ones, listed in one rule of its own guidelines with what each checks and what a failure costs, held to all the shared checks are held to; whether one refuses or reports is decided by that rule, which its owner confirms, and not by the settings of the tools.