Six ways GitLab CLI documented itself wrong, and the two CI traps I hit finding them
go
dev.to
Before the July 2026 GitLab Hackathon I spent a few days reading gitlab-org/cli, the Go source behind glab. I wasn't hunting for crashes. I was looking for places where the project contradicts itself: one part of the code deprecates something, another part still tells you to use it. Six of those turned into merge requests. Here's the technique, what it found, and two CI traps that almost stopped any of it from landing. The technique: grep the deprecation, then read the help text Cob