Rules as checks
The idea
A team rule that can be checked gets a checker for a pattern, a name, a structure, a command or a benchmark. The checker runs on the change before a pull request, on each push, before the worker finishes the task, and during verification.
- The problem
- A model can easily break team conventions that exist only as prose.
- Why it matters
- A rule with a checker holds the change until someone fixes or waives it.
- Where it stands
- In production as of
A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.