Open
Description
Currently auto-merge is only supported if Digger jobs are started directly via action triggers (not by the backend). This is due to historic reasons; initially Digger did not have an orchestrator backend.
This is one of the many things that the orchestrator needs to start doing when all jobs are complete. This likely requires some kind of a resilient async state persistence; we could use our Postgres DB for that or a dedicated queue like Redis or some other way.
Reported by the user A.T.