> On Fri, Apr 1, 2022 at 4:27 PM Robbie Harwood <rharwood(a)redhat.com> wrote: > > Why not this then: > > - fedpkg commit -sc && fedpkg scratch-build --srpm && fedpkg push > && > fedpkg build > > Yes, it'll still take longer, but you won't need to context switch > unless the scratch build fails (which would make you do a fixup commit > + another build anyway). This workflow allows you to amend the commit > until you get a successful scratch build, after which it is unlikely > that you would need to commit another fixup. Well, sure. That's what I'm doing. (Basically; since when do we sign off on dist-git?) I guess you missed my main point: What to do when a wrong commit is pushed but is not built yet? Answering "Don't push wrong commits." is only of limitted help - especially when these commits come from other people ... If everyone makes sure they check their stuff before and do not scratch-build from a dirty tree and the build not only succeeds but the results work then there is no problem to solve in the first place! But I guess the real solution is to give up on a tidy dist-git history. Makes you sleep much better :) _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
