This is not relevant for now

do not publish the detailed reasons in published report

The email notifications will be a bit fancier

Only output checks that ended to an actual state transition.

never forget to reset the intermediate list...

sometimes gitlab API does not send stable information about MRs, like
mergeability.
Add a Quantum state to the graphs that forces homer to do nothing as
long as it cannot get stable info.

See #6

use keyset pagination mode that adds a "link" header compliant with
https://www.w3.org/wiki/LinkHeader

gitlab CI artifact management for schedules seems complicated.
Go back to something simple and straightforward (build then launch), as
homer is extremely simple and has no dependency.

Notify users homer-bot messages are sent by a bot.

As the content of the notes are also sent through emails, do not use
html/pseudo html in messages.

Use empty links (like [](...) ) to do the same as html comments.

Some conditions should not be displayed if they fail: the Silent
parameter removes that.

This probably will be quite slow when we have lots of succeded jobs.
Need to figure out a way to filter on job names server-side.

If pipeline is not finised (pending, running, etc.), we do not want
to have confusing labels/states. So remove any label in this case.