This is a great perspective: bug reports should be clear, with reproduction instructions, but they need to be persuasive too.
Related Posts
It's a small thing, but I'm much happier with the output of --version in the latest version of difftastic.
It shows the release version number, the commit hash, and the commit date. This gives you a sense of the age of release, but you still have a reproducible build (unlike build time).
It also shows OS, arch and compiler, because those are common requirements in bug reports.
Chekhov's repro: If a line of code is included in a bug report, it should contribute to the debugging somewhere.
"After I linked difftastic, one of my friends immediately used difftastic to find a stealthy bug, five stars!"
https://www.scannedinavian.com/tools-built-on-tree-sitters-concrete-syntax-trees.html