Recent searches
Search options
@michelin@hachyderm.ioWonder how many @packit PR you merged while automating your @fedora #Packaging #workflow ?
The #Pagure API does not let you answer this directly, so if you're wondering like me (or want to answer similar questions re: your PR activities), help is here!
$ ./distgit-pr-stats.py salimma --closed 2024-01-01..2025-01-01 --per-page 100 --requester packit --status Merged
https://michel-slm.name/posts/2025-01-07-distgit-stats/
This post is day 27 of my #100DaysToOffload challenge. Visit 100daystooffload.com to get more info, or to get involved.
Pensées de Michel · On querying your Fedora dist-git PR statisticsOver the course of 2024, I’ve been increasingly adopting Packit’s pull-from-upstream for automating some package updates. I still think it should only be used judiciously - e.g. I generally only enable it for packages that do not embed code from other projects (necessitating license audits each time) and have good test coverage (because I’ll merge the PR if the test suite and installability checks both pass). Some packaging ecosystems that require the RPM spec to be regenerated each time (such as Rust) are disqualified by default. In fact, FESCo just voted today on the Automated Packit onboarding Change Proposal - and approved it provided it’s opt-in rather than opt-out, given these and similar concerns that several members share.