The AI PR that silenced the type error with an ignore comment
I keep hitting this one in AI-written PRs. The ticket is a real bug or a typed interface change. CI was red on types or lint. The agent "fixes" it with // @ts-ignore, # type: ignore, eslint-disable, or a cast to any rig
I keep hitting this one in AI-written PRs.
The ticket is a real bug or a typed interface change. CI was red on types or lint. The agent "fixes" it with // @ts-ignore, # type: ignore, eslint-disable, or a cast to any right on the failing line. Diff is tiny. Summary says temporary. Merge temptation is high.
The type checker just lost its job on that path. You did not ask for that silence.
The 60-second check I run now
When an agent PR adds ignore comments, blanket disables, or new any casts near the change:
- Diff only the ignore/disable/
anylines — what exact error did they hide? - Ask: did the ticket need that silence, or did the agent use it to green CI without fixing the type?
- If the ignore landed without a typed fix or a tracked follow-up, I bounce it or split it. Temporary ignores in a merged PR are not temporary.
This is one of the stops on a short bar I use before I merge agent PRs. Free one-pager if you want the rest: https://chopragunji.gumroad.com/l/zpnmdn
If you'd rather someone else do a hard pass on one scary AI PR, I still have founding slots at $49 (normally $99): https://chopragunji.gumroad.com/l/byoyi/FOUNDING
Has an agent on your team ever greened CI by ignoring the type error instead of fixing it?
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.