All your checks are green. Before you merge, one question worth asking: is it green because the code...
All your checks are green. Before you merge, one question worth asking: is it green because the code was fixed, or because the checker was silenced?
There are two ways to turn a red CI run green. You can fix the problem, or you can make the tool stop reporting it:
Type error? as any or # type: ignore makes it vanish.
Failing test? it.skip or @pytest.mark.skip takes it out of the run. Or it.only quietly skips everything else.
Linter warning? eslint-disable or # noqa and it's quiet.
An AI agent can make CI go green without making the code right. Here's how that happens, and how far you can get catching it.
A CLI and GitHub Action that scans AI-written pull requests for sketchy patterns and posts the findings back to the PR. Advisory…
Semgrep and ESLint flag risky code. This flags what they miss: tests weakened, errors swallowed, renames left half-done.
An AI-generated test that passes proves nothing until it can go red. Mutation testing exposes the phantom tests, with a Go…
We are all using AI to write code now. Whether it's Claude Code, Aider, or Copilot, the speed is...
To audit AI-generated tests, score how many mirror the code instead of checking it. Green CI proves...
