Hi Tome & the packit team!
(sorry for resurecting this old thread, I'm working through my backlog…)
As a co-maintainer of the exiv2 library, is there a way for us to use
packit that makes sense? I guess not for the master branch, as we are
currently reworking the API and will probably only cause the CI to be red
all the time. But could it work for our 0.27 maintenance branch only?
There we are backporting bugfixes only and try not to break the API, but
have currently no way of really checking that (bonus points if packit
includes a rebuild+retest of packages depending on exiv2).
Tomas Tomecek <ttomecek(a)redhat.com> writes:
We are happy to announce the availability of Packit-as-a-Service
a GitHub App, which utilizes the Packit project .
Using the Packit service in your upstream projects helps you
continuously ensure that your projects work in Fedora OS. Just add one
config file  to your repository, along with the RPM spec file and
you're almost there. We have started publishing docs for the service
over here .
In the next couple of months, Packit Service will run in an
invite-only mode, where we need to manually approve every user of the
app. Our initial target is Fedora contributors.
Packit service validates your pull requests by building your software
in Fedora OS. Once the builds are done, Packit lets you know how to
install the RPM with the change inside your environment.
Packit service helps you test the changes before merging them to the
main developer branch and shipping them to your users.
The packit team
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines