cc @adamwill
When we update Python, we use a Pull Request-based approach. I would very much like to see the results of the OpenQA tests before we merge and build and Bodhi the update. I believe that discovering issues in Bodhi is too late -- what doesn't work should not be committed to dist git.
This isn't a high priority, because OpenQA test failures in Bodhi only happened once for Python. But would be nice to have.
This is possible, and on my list to look into, but it's not the highest priority. The best place to file it would be https://pagure.io/fedora-qa/fedora_openqa/issues - openQA is not a part of Fedora CI.
It will be much easier to implement if there is already a system that automatically produces a scratch build with the PR included, and that system publishes a useful fedora-messaging message when the build is complete (by "useful" I mean, it provides enough information to locate the scratch build, and to associate it with the relevant pull request).