Hello :wave: I started using marge-bot for automatic merge-queue handling and first trying the simple approach running it in [GitLab CI](https://gitlab.com/marge-org/marge-bot#running-marge-bot-in-ci) as scheduled pipeline job (each 5 minutes). First investigations: * during the runs it takes some time to process the assigned MRs * marge bot is blocking on each MR and waits for CI to finish * depending on CI pipeline it can take minutes to hours to finish them Questions: * what is the best strategy to configure the `MARGE_CI_TIMEOUT` ? * we know it does not make sense to wait for the pipeline in "blocking mode" * should we set it to `0` or some minimum seconds timeout `5s`? * if the timeout is reached, can we prevent marge to re-assign to originator as we know next run will check the pipeline status again and just merge if already succeeded? We are receiving comment like this `I couldn't merge this branch: CI is taking too long. See pipeline...` and marge removes or changes the assignee to the originator. Is there a way to prevent this workflow and in case of pipeline timeouts just comment or skip as next try will check it again and see pipeline is still running? Thanks :smiley: