We've discussed this idea many times but strangely I can't find an issue about it.

CiBoT for the prechecker needs some memory, if it was able to know....

Given a remote+branch combination:

1. What the commit hash it last checked
2. What moodle.git hash it last attempted to merge to

We could get rid of the 'ci' label and make the prechecker continually check for new branch updates and precheck them.

This would mean that:

• Last minute changes are prechecked (we would be checking for updates near instantly and only doing work when a branch has changed)
• There wouldn't be any pointless cibot noise doing repeated work

Additionally if we stored the 'success', we could avoid doing tracker updates when everything is 'green'.

A further thought, if the brain was decent, we could also replace 'ok' cibot tracker updates with a gha-like dynamic button instead of a noisy comment. (But maintain the comment in the case of failure).

I know that when Eloy and I have talked about this before he's been thinking along the lines of a basic text file. But the more I think about it, the more I think that making this 'brain' a local plugin Moodle plugin with some web services might be a solution. It can start off as a simple key/value store, but we can potentially build more on top of it. The jobs do as they do now, with a few hooks in to call webservices to check if they need to operate on issues.