#github-actions (2020-10)
Discussions related to GitHub Actions
2020-10-19
![Alencar Junior avatar](https://avatars.slack-edge.com/2020-10-05/1407799829122_3931e85fd61a9272f913_72.jpg)
Has anyone looked at deploying multiple branches by triggering github actions across different repositories?
2020-10-28
![sheldonh avatar](https://secure.gravatar.com/avatar/b909e5a82474e9853ff6a6c6111cf0cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0020-72.png)
Using github actions more now, but here’s something I don’t like. Maybe there is a solution?
I’m combining a lot of my “systems management” oriented work into a single repo rather than many small repos for the sake of simplifying management and contribution. This approaches a small mono repo format.
The github action checks are a bit annoying here as if I link up terraform cloud workspaces + more then it shows this huge list of 15+ checks that are all “Path not changed, no run triggered”. Is there a way to simplify/hide/group checks so that this noise is reduced for a contributor?
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
I agree that the status checks can get annoying - we have one repo with over 500 status checks
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
This happens if using a lot of workspaces in TFC too
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
In the end, I think GitHub will have to release some UI improvements to accommodate for it
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
Also frustrating is is we want to use branch protections to require checks to pass, but not all checks trigger on all PRs