Marge-bot unnecessarily duplicates pipeline on the same commit

Hello! Thank you for your project — I'm a recent user, currently evaluating Marge-bot on one of the projects I maintain.

I have observed the following behavior:

• Marge-bot insists on creating its own pipeline on the same commit.
• Worse, GitLab’s interruptible: true pipelines feature does not help here, since both pipelines are for the same commit — meaning the new pipeline won't cancel the first one, causing extra resource consumption.

My setup:

Image:

registry.gitlab.com/marge-org/marge-bot:0.15.3, same with 0.16.0

Config flags:

--use-https
--rebase-remotely
--ci-timeout=30min

Illustrative image:

Suggestion for improvement:

• If a pipeline already exists, Marge-bot should not create a new one and rather wait for the status result.
• Is it possible marge-bot doesn't check for status of pipeline for the commit from gitlab api?
• Could be related to #428 as marge-bot makes decision on outdated local git checkout version of the repo instead of using gitlab api for merging.