[connabyss]

Requested by CH · project thread

What was wrong, what you changed, how you checked:

I ran v0.11.0's comeback alarm over the last 300 commits of each of the 19 scoreboard projects. It only reads git history and runs no tests. It fired "UNDONE BY A LATER COMMIT" 13 times, and I checked each one by hand:

• 6 were wrong. In 5 of them a later commit did the fix another way: marshmallow 19ca8dce (its later commit even says "the allow_none fix from #2894 is preserved"), more-itertools 6b1907de, serde_json a95d6df9, and indexmap cf9397ff and 6a838832. The 6th was a tidy-up done another way (bytes 0c17e992, "ci: silence warnings").
• 2 were reverts coming back: click 8ee83ddb and JSON-java 94341cd6. When the commit Bite checks is itself a revert, putting the code back re-applies the original change. No fix came undone.
• 1 named the wrong commit: on testify, d5be4144 (inside the default --last 40) named the merge "Merge pull request #1935 … yaml-update". The commit that actually put the old code back is 15f6826.
• 4 were real, deliberate undos, and they still get the alarm (anyhow 10370e94, marshmallow 99e28645). JSON-java 1de42aa4 and serde_json 83bdc5fd are now read as "done another way", since their later commits rewrote the same function.

Changes in came_back:

1. If the commit that took the fix's lines out also wrote new code of its own in a function the fix changed, Bite treats it as a rewrite and gives no alarm. Lines put back and comments don't count as new code. The commit then gets the normal free check.
2. A checked commit that is a revert, or a tidy-up, gets no alarm.
3. The commit Bite names is the newest one where the fix went missing while its parent still had it. A merge is named only if the merge itself dropped the fix.

• For a bug fix: there's a new test in tests/test_comeback.py for each of the 4 cases. All 4 failed on main, and each one fails again when its own part of the change is taken out.
• python -m pytest passes: 172 passed. The try-to-trick-Bite harness didn't get worse: 29 ok vs 28 in the last saved run.
• After the change, the same 19-project scan leaves only the true undos as alarms.

Assisted-by: Claude Code

---

Generated by Claude Code

[github-actions]

✅ Bite-proof. Nice work.

Bite took each change out, one at a time, and a test noticed every time. If one breaks later, that test will warn you.

Badge for your README: [![Bite-proof ✅](https://img.shields.io/badge/Bite--proof-%E2%9C%85-black)](https://github.com/connabyss/bite)

• ✅ The tests test_the_culprit_is_the_commit_not_the_merge_that_brought_it_in and 3 more noticed it was gone. If this change breaks later, they will warn you.
  _{Commit 223e52f0: “Comeback alarm: no alarm for a fix done another way, and name the right commit”}

How Bite checks

Bite asks one question about each change: if it disappeared, would any test notice? It takes the change out, runs your tests, and puts it back. What is Bite?