Full ack. When I maintained ~ 400 packages, the only way ship them was to have a CI building them in a clean environment and autopush them on successfull builds.
But you haven't actually tested the package installs, does the software work? Why do you think there are Arch Testers? To ensure that all the core packages are properly tested, no matter how important. Just because Arch Linux is rolling release doesn't mean we should throw stability right out the window!
Before I had this, packages were broken all the time. Clean build should be necessary before pushing any package, not just ones built by a CI.
Clean builds are fine to automate, just as long as they are reviewed after the build, before pushing it. Makepkg clearly shows warnings which could caause the package to not function as it should, you can't just assume something which is built works, and have a CI/CD task push it to the AUR. The reason that Arch TUs can maintain 1000-2000 packages each is because they have the Arch Testers, they can push a new build and get it tested by someone else. In the AUR, you do not have this luxury, simply stop being lazy and test the damn package, or orphan it for someone else to take your place. Or if you have a large following, employ your own testers for your packages :P -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev