On Mon, 2021-01-25 at 11:40 -0500, Matthew Miller wrote:
On Mon, Jan 25, 2021 at 04:43:21PM +0100, Fabio Valentini wrote:
> But that would involve at least six new steps that would've to be
> automated: 1) Creating a fork on src.fp.o (plus error handling
> around
> already existing forks), 2) Cloning the fork instead of the main
> repo,
> 3) Automatically creating a PR after a git push, 4) Automatically
> merging the PR if CI passes, 5) Deleting the fork, 6) Automatically
> building the package in koji ...
Yeah, honestly, this is also a pretty serious hardship for the long
tail of
people maintaining a handful of infrequently updated packages. I'm
hugely in
favor of not checking in work in progress on the main or release
branches,
but let's not make more steps.
Similar to the (optional) playground repo we have for epel8 -- would
having a 'rawhide-playground' repo help?
Best regards,
--
Michel Alexandre Salim
profile: https://keyoxide.org/michel@michel-slm.name
chat via email:
https://delta.chat/
GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2