Tristan de Cacqueray

Perhaps such metrics could also be collected through an external tool, e.g. by running the relevant queries using a sliding window or something. Then the web interface could expose such...

It seems like only the `changes` query let you get a complete list of document. Perhaps a similar query could be implemented for `authors`. Then for the list of well...

Hey @georgettica , it seems like the memory requirements are missing from the doc, it should indicate that building the image needs more than 2GB of memory.

I meant release branch, or do you prefer we create a project per release? E.g. using a tuple (project name, release name).

Could we use a different index instead of adding a new document _type?

Note that the identity configuration now enables setting group, this was implemented with https://github.com/change-metrics/monocle/pull/438

Please re-open if needed.

Perhaps commenting is more of contributor task. I meant to associate the maintainer role for merged change event.

Hi, I think this would be possible with https://github.com/change-metrics/monocle/issues/522 . Until then, setting `not group:bots` in the query should do the trick.

This is not so simple to do, in the linked PR it can do: `state:open and author:"John Doe"` -> `state:merged and author:"John Doe"`