This document discusses using a tool called "git ratchet" to automatically track and enforce performance metrics over time in continuous integration (CI) builds. It notes that static analysis is underused, introduces are hard, and regressions can be hard to detect. It then describes how git ratchet would measure performance metrics during CI builds, store the data in git notes, and fail builds if metrics increase over baseline values, helping to "ratchet up" performance and catch regressions early. Examples shown include tracking JSHint warnings and page weight over time. The document encourages providing feedback on git ratchet to further improve continuous integration and monitoring of performance measures.