koji_build and bodhi_update jobs.
For both of them, the behaviour is the same as for pull_from_upstream - the configuration is taken
from the default branch of the dist-git repository (usually rawhide) and other branches are ignored.
(packit-service#2295)Let's see what happened in Packit in 2023.
We, the packit team, are happy to invite you to our upcoming workshop about pulling upstream releases to Fedora using Packit.
When: Wed, Jan 10, 9:30 AM - Wed, Jan 10, 12:30 PM (GMT+1)
Where: Online!
Who should attend: Anyone who maintains a package in Fedora or EPEL and would like to automate syncing the upstream releases for it. The automation is most suitable for simple packages with straightforward update processes (e.g. without patches, or need to build in side-tags). It works without access to the upstream repository.
No package? It’s not an issue. The workshop can help you understand the Fedora release process and the services involved. During the workshop, you can help someone else automate their package or ask someone around if you can help with the maintenance (that’s usually very welcome!). You can also bring an orphaned package back to life!
Can’t make it this time? You can also follow our documentation and ask for help in case of any issue: #packit:fedora.im (Matrix).
If you want to join us please fill this form or contact us on Matrix, and we will send you further details!
Looking forward to seeing you!
Let's see what happened in Packit in 2022.
Let's see what happened in Packit in 2021.
Let's see what happened in Packit in 2020.
Let's see what happened in Packit in 2019.
