By Eric Gitangu. Originally published at developer.ericgitangu.com .
I work on the backend of a mobility/fintech platform. This post is about adding a linter to code that was already running production, and about the day the linter turned out to be grading the wrong checkout.
The problem
The shell scripts in our repo are not side projects. They deploy production, apply configuration and decide whether a merge is allowed. They were also the one kind of code with no automated check. The backend had a static analyser with a baseline. The scripts had code review and hope.
Turning a linter on in old code usually ends one of two ways:
Fix everything first. A week of diffs nobody asked for, in the scripts you least want to touch.
Warn only.…