The blog post discusses dissatisfaction with GitHub Actions due to its limitations in managing complex workflows, especially in monorepo setups with certain features like pull request checks and workflow reusability. Several issues have been highlighted, along with alternatives for GitHub Actions.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Using GitHub Actions for a large team with a monorepo setup can be challenging. Issues include managing dependencies for required checks, maintaining numerous workflow files, and handling limitations with conditions and workflow reuse. Alternatives like GitLab, Jenkins, and TeamCity may provide better solutions for CI/CD. GitHub Actions lacks features and improvements to better handle complex pipelines and requirements, causing frustration among users.

I'll think twice before using Github Actions again

<blockquote>
<p>In GitHub you can specify a “required check”, the name of the step in your pipeline that always has to be green before a pull request is merged. As an example, I can say that web-app1 - Unit tests are required to pass. The problem is that this step will only run when I change something in the web-app1 folder. So if my pull request only made changes in api1 I will never be able to merge my pull request! 🤯</p>
</blockquote>
<p>We have a pretty similar setup, and here’s how we solved the problem above: there’s a command that runs all the unit tests in the project. And we have a tool that returns test match only for files that have changed. So in CI, there’s one required job that will run all the tests, but the tests will only run for the changed files, and so this essentially works in any CI setup, because it’s no longer about CI, but about detecting the correct test match</p>
