I remember that during the Python 3.8 rebuilds in the side tag, one package had
this automated somehow already. I was bumping the release/changelog and trying
to build it in the side tag at least 5 times, but I was building with
--background, so the automation always got the NEVR in Koji first.
I guess it is python-gear ? Where I'm experimenting some automation based on Zuul CI.
There is a job triggered to build in Koji when master ref change. This job can be trigger
instead when a PR is closed/merged, that way direct push will not trigger a build.