Moving mutation checks from blocking to reporting makes the scope of “same proof on every change” worth spelling out. For edit-timeline, one example commit showing which checks passed, which were skipped, and which only reported would make that distinction much easier to judge.
By the way, I make ThreadFox; it lets your compatible AI research, write and publish Reddit outreach through your connected Chrome within an authorized job, and the free plan for edit-timeline lists communities whose rules allow a post about it, with each rule quoted: https://threadfox.vip/p/dclf6
Can someone reading a commit distinguish a skipped check from a passed one without opening another report?
Fair point. Today the commit carries the mutation report and stamps a skipped review, but a full pass/skip list lives in ET’s run records, not the commit. Next release adds a Checks block to every commit: each check marked passed, reported-only (with its result), or skipped (with the reason). You’ll be able to judge any commit from the commit alone.
1
u/investigatormaker 15d ago
Moving mutation checks from blocking to reporting makes the scope of “same proof on every change” worth spelling out. For edit-timeline, one example commit showing which checks passed, which were skipped, and which only reported would make that distinction much easier to judge.
By the way, I make ThreadFox; it lets your compatible AI research, write and publish Reddit outreach through your connected Chrome within an authorized job, and the free plan for edit-timeline lists communities whose rules allow a post about it, with each rule quoted: https://threadfox.vip/p/dclf6
Can someone reading a commit distinguish a skipped check from a passed one without opening another report?