Aleks-Daniel Jakimenko-Aleksejev

FWIW I'm against early detection. Some bots (e.g. Notable) don't need zstd at all, and unicodable does not need it in most cases. Maybe one way to do it is...

> Testable is probably not a good place, since it's, well, only in the test directory. So? Meaning that if you run tests, you'll get an error relatively early. If...

My newest idea is to make something that detects code blocks in tickets and edits them by adding output from committable and bisectable. This way you won't need to learn...

Mostly this is about cases when we have more than one commit to report, like [this](https://gist.github.com/1176206b14ad722b53e6c6e920e60357). Yes, I think it would be better to have .md file there.

Would be great if someone took an existing output file (for example [this one](https://gist.github.com/Whateverable/13556140482322fd5bf4080092a1d284)) and turned it into a markdown document. Then I'll easily change the code so that it...

There are tests for bisectable, evalable and committable. Should we add tests for other bots too?

Ignore this comment, I'm testing github markup: for 1…∞ { say 42 }

Also doesn't work with nicknames that have numbers in it.

I agree. Personally I did use it a few times (it was something like `2018.10..HEAD` when there were not many commits after the release, also I remember doing something like...

I don't think this is fixed (though both bots should behave exactly the same now).