Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Tuesday, 19-May-2026 08:41:04 JST Rich Felker

   @whitequark @wwahammy I think I'm one of them so I'll go over a few:

   1. Resource usage externalities when this is done at scale, especially for large projects times large numbers of PR authors. This manifests as energy waste, hammering the servers/infrastructure of software you depend on and pull dynamically in standard "destroy the world and re-run everything from scratch" CI recipes, etc.

   2. Dependency on subsidized compute resources from a capitalist platform with motivation to lock you in and enshittify.

   3. Reducing or eliminating the mandate for your software to be independently buildable by people on their own systems without your CI infrastructure.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Tuesday, 19-May-2026 09:15:12 JST Rich Felker

     in reply to

     • ValorZard

     @valorzard @whitequark @wwahammy Well I'm against a number of standard CI/CD practices that are harmful to parties not even involved in the project using the CI/CD.

     I don't have a specific recommendation for something I haven't wanted to use. I don't think the whole purpose of CI/CD is that important because I don't think we should be expecting non-developers to be using a continuous rolling main branch rather than discrete releases the maintainers have confidence in. If other people want to do that, fine, but finding the right tooling to do it without externalities impacting others is on them not me.

   • Embed this notice
     ValorZard (valorzard@mastodon.gamedev.place)'s status on Tuesday, 19-May-2026 09:15:13 JST ValorZard

     in reply to

     @dalias @whitequark @wwahammy ok so your not against CI/CD, your just against GitHub Actions specifically.

     What would you recommend instead?