GitHub Actions is criticized for its shortcomings in continuous integration (CI) processes. The author, with extensive experience across various CI systems, argues that GitHub Actions fails to deliver a reliable and efficient user experience. Navigating through error logs is cumbersome. Users often face multiple clicks through various pages just to identify a failure, experiencing slow load times and an unreliable log viewer that can crash browsers. This frustrating cycle can consume an entire afternoon as developers struggle to debug issues, highlighting a lack of intuitiveness in the platform. The YAML configuration used in GitHub Actions adds another layer of complexity. The author describes it as convoluted, with a confusing syntax that evolves in unpredictable ways. Users frequently encounter issues when trying to set environment variables conditionally or when dealing with intricate expressions. This leads to a steep learning curve, where understanding comes mostly through trial and error rather than clear documentation. The GitHub Actions Marketplace, where users can find community-maintained actions, is painted as a risky environment. Developers often unknowingly grant access to their repositories and secrets when using third-party actions, raising security concerns about the opaque nature of these external scripts. Furthermore, GitHub Actions relies on Microsoft’s runners, which are slow and limited in customization. Users can't control the compute environment effectively, leading to inefficiencies, especially for larger builds. Developers may find themselves facing increased costs if they need more powerful runners. The article suggests that these issues can detract from productivity and morale within engineering teams, raising questions about the suitability of GitHub Actions as a CI solution compared to alternatives like Buildkite.