Hi,
just adding some background information about the CiBoT and its checks...
Since long ago, we have a "manual" checker that, under demand, was able to perform some basic checks (mergeability, codechecker reporting filtering results by changed lines, phpdocs...). And we (the integration team) have been using it manually as a helper tool in the integration process.
But it was clear since time ago (MDLSITE-2287) that the same tool could be really useful not only for integrators, but also to developers and peer-reviewers, so we have been thinking about to automate it under various situations, namely:
- when a developer requests it by adding the "cime" label to the issue (this is already automated, feel free to try it, should work).
- when an issue goes to "waiting peer review" status (not automated yet, just deciding about its schedule).
- when an issue goes to "waiting for integration" status for us, integrators, to have a fresh report (not automated yet, just deciding about its schedule).
All those executions are run from the "Tracker - CI - Bulk precheck issues" job in the CI servers and we have just performed some public runs of them lately (note there is a setting in the jobs to make executions quiet, we just moved to "verbose" mode recently).
Before running those new "verbose" executions I did add a comment warning about the incoming CiBoT report. I just did not add that explanatory comment for the last manual run and that's the one pre-checking MDL-26680 (and another 35 issues).
Basically, we are performing some runs here and there, and any feedback, comments, problem, subtasks... should go to MDLSITE-2662 where we are aiming to polish the bulk pre-checker as much as possible before making it public (although I suppose it's already public LOL).
In any case, be warned it:
- Is still experimental (wip).
- Is still incomplete (there are tons of checks to add to it).
- It can show some false positives here and there (we need to tidy/conform some of the checks to be more accurate).
And, as said, all that is happening @ MDLSITE-2662, feel free to comment there. For example I jut have created a subtask of it (MDLSITE-2689), aiming to clarify a bit the comments added by the bot(s).
And that's the story and the history of the CiBoT pre-checker and how we want it to become a good tool for everybody. Let's see how it evolves.
Hope this helps, ciao 
