On 02/12/2022 18:20, Jakub Kadlcik wrote:
I started working on a service [2] that listens to fedora-messaging and for every new RHBZ review ticket or a new comment with updated packages, it submits a build in Copr. Thanks to this [1] feature, Copr automatically runs the fedora-review tool and generates the review.txt file. Once the build is finished, my service gets the message and generates a helpful comment (so far only to STDOUT).
fedora-review require a lot of manual checks from reviewer (especially licenses). It can't be fully automated.
But posting this as a template for the reviewer is good idea. +1. -- Sincerely, Vitaly Zaitsev (vitaly@xxxxxxxxxxxxxx) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue