Back to listCategory config Workaround hack Stage deploy Freshness persistent Scope single_lib Upstream stale Recurring Yes Buyer Type team Maintainer abandoned
Required checks cannot dynamically match triggered workflows in monorepos
8/10 HighGitHub Actions requires explicitly naming required status checks, but in monorepos with dynamic pipelines, only relevant checks should be mandatory. If a PR only touches `api1` but `web-app1` checks aren't triggered, the PR cannot merge even though all relevant checks passed. This forces developers to run unnecessary pipelines just to satisfy merge requirements.
Collection History
Query: “What are the most common pain points with GitHub Actions in 2025?”3/27/2026
If my pull request only made changes in `api1` I will never be able to merge my pull request! Working around this limitation is hacky, difficult to maintain, and costly since you have to run additional pipelines just to determine if a pull request can be merged or not! It's been almost 3 years since these issues were raised, and nothing changed yet!
Created: 3/27/2026Updated: 3/27/2026