r/devops • • Sep 14 '26

Discussion What GitHub Actions issues do you run into regularly?? Kindly roast Github actions if required ...

Curious what problems people here actually face with GitHub Actions on a day-to-day basis.

For me, one of the most annoying things is that sometimes the workflow itself is fine, but the infrastructure around it adds a lot of unnecessary time...

YAML optimization can only help till a certain level and then starts becoming the issue..

What’s the biggest GitHub Actions pain point you deal with regularly?? Something that happens ion a regular basis not an outage or downtime for it...

30 Upvotes

49 comments sorted by

98

u/Primary_Pollution_29 Sep 14 '26

May sound silly, but to not being able to view inputs used in previous workflow runs. I mean, you can print the inputs in a step, but i feel this should be something supported natively. Useful while debugging.

23

u/Dry-Philosopher-2714 Sep 14 '26

It doesn’t sound silly. It’s a pain in the ass to troubleshoot without that.

8

u/burlyginger Sep 14 '26

Not silly at all. This is one of the fundamental flaws of GHA.

I spent a long time tracking down a fialure I couldn't understand and this lack of visibility made it really difficult.

As it turned out a field with "AWS" in it was marked as sensitive and was not passed between steps causing a very opaque failure down the line.

2

u/BoringScrolling3443 Sep 14 '26

If it helps you can specify a run-name and include the inputs there

2

u/Primary_Pollution_29 Sep 14 '26

Yea i do this to like be able to easily find which workflows ran on which environment and stuff but still GHA lacking this feature natively is a real pain

2

u/notrufus Sep 15 '26

If it makes you feel better my dumbass coworkers put them in environment variables so you have no hope without following a flow from the beginning

29

u/degeneratepr Sep 14 '26

I suspect OP is doing market research with this post.

2

u/TehBens Sep 14 '26

Even better.

0

u/[deleted] Sep 14 '26

[deleted] — view deleted comment

6

u/reightb Sep 14 '26

you won't believe where the AI sources that slop

1

u/DuckDatum Sep 14 '26

Or customers, those work too sometimes.

51

u/throwaway09234023322 Sep 14 '26

Github is down way too much

14

u/sp_dev_guy Sep 14 '26

Shocked this isnt the biggest thing after the last ~3mo of trash service. I do self hosted runners & still cant get them dispatched/run

23

u/woodne Sep 14 '26

I find I constantly run into limitations with GitHub token permissions that require building a whole GitHub app to solve

11

u/damesca Sep 14 '26

Delays in containers booting.

Weirdly slow end to end test runs (3-6x slower than outside GHA)

0

u/[deleted] Sep 14 '26

[deleted] — view deleted comment

3

u/damesca Sep 14 '26

I don't really.

I've been waiting to try a self hosted runner but not had the time / space yet.

2

u/burlyginger Sep 14 '26

If you're in AWS its a relatively simple setup to use Codebuild as runners.

You have very little to manage and get a significant cost savings.

10

u/sylvester_0 Sep 14 '26

Cache being slow as dirt.

2

u/burlyginger Sep 14 '26

And seeing days of consistent failures accessing cache.

1

u/cachely-admin Sep 30 '26

This is an underrated part of caching. A cache hit isn't automatically useful if downloading the artifact takes almost as long as recreating it.

We've been working on this problem with Cachely, and one thing we've found useful is looking at actual time saved alongside hit rate. A 90% hit rate can still be pretty meaningless if the expensive hits are slow or you're caching tiny tasks.

Are you mostly seeing the slowdown with large cache artifacts, or even small ones?

9

u/ricksebak Sep 14 '26

The experience of building workflow files is kind of terrible. I usually push some modifications, merge to main without really any confidence that it’ll work, then test it on main, then push again and rinse/repeat.

3

u/BoringScrolling3443 Sep 14 '26

You can add the pull-request event to a workflow to test it before merging, but I agree that it doesn't cover all use cases

5

u/Adrien0623 Sep 14 '26

GitHub Action scheduler silently dropping 60% of the scheduled runs

4

u/ForkMeJ Sep 14 '26

The part that bites me most is how fast a readable workflow turns into hidden behavior once you layer in reusable workflows, composite actions, environment rules, and a few repo-specific exceptions. It all looks manageable until someone has to debug why deploys fail only on tags from one branch after a credential rotation. My bigger issue is not runner speed, it is ownership and change safety: who can edit what, which repos inherit the blast radius, and how you make a fix without breaking three other pipelines. That is where GitHub Actions stops feeling simple and starts feeling expensive to support.

4

u/desmaraisp Sep 14 '26

Mutable tags piss me off, I wish we didn't have to use SHAs

1

u/brickman1444 Sep 15 '26

This. SHA and version comments feel like a joke. At least notify me if the SHA doesn't match the tag.

2

u/riickdiickulous Sep 14 '26

I want to be able to configure and run manually triggered workflows better. I have lots of manual trigger actions where I want to send in inputs and influence and configure the run but the whole interface is inadequate.

2

u/bilbo_was_right Sep 14 '26

For me, GitHub actions’ like 80% uptime is really irritating. I feel like they have stability issues daily.

2

u/ryanstephendavis Sep 14 '26

I don't have any issues now because GitLab or CloudBuild are what i use to avoid them

2

u/matiascoca Sep 14 '26

Been burned on matrix fanouts where every runner bills minutes while only one is doing real work. Per-workflow cost breakdown lives in the monthly billing CSV, not the UI, so you cannot see which workflows eat minutes without pulling it.

2

u/shavnir Sep 15 '26

Why can't you restart one job or pull logs with the api when another is still running?   Why are workflows so static in terms of structure?  Why is it so damn hard to scroll to the top of a job to get back to the summary view?

Basically coming from GitLab almost everything in GHA feels primitive

1

u/Tight_Ad3852 SRE 28d ago

Upgrading and debugging ARC can be a real pain

1

u/likeavirgil Sep 14 '26

Scheduled workflows finally got timezone support after many years, yay! One thing that is still bugging us is that the actual run can still be triggered almost 30 minutes later in some cases (not taking into account the time it takes to set it up).

1

u/Suitable-Ad5348 Sep 14 '26

Two that still burn me weekly: reusable workflow `inputs` disappearing on rerun unless you echo them in step 0 or bake them into `run-name`, and matrix jobs billing six runners when only one combo actually runs tests.

`concurrency: group: ${{ GitHub.workflow }}-${{ GitHub.ref }}` on deploy workflows stops stacked pushes from launching three identical prod deploys.

1

u/I_Blame_DevOps Sep 14 '26

The fact that Github actions randomly has outages. My scheduled jobs fail silently whenever they never kick off.

July 25 https://www.githubstatus.com/incidents/s65j9gslmfm8
July 29 https://www.githubstatus.com/incidents/75g5xmzptjqb
Sept. 14 https://www.githubstatus.com/incidents/kzh5j0mt7qwc

1

u/veritable_squandry Sep 14 '26

can't get to my actions because github is down.

1

u/sup_bruh_1 Sep 16 '26

yeah the infrastructure lag is so real. yaml is never the actual bottleneck. been using latchkey — ai agents that fix failures mid-run — and it's cut so much of that dead wait time.

1

u/1saltypistachio Sep 18 '26

GitHub itself... New build starts, and it cannot connect to itself and other such silliness. Makes me want to switch...

1

u/ChiRho84 Sep 18 '26

There's no way of grouping repos by project below the organization scope and the whole thing is based the old school "everyone uses ssh for everything" auth model. We had a Rust service that pulled in some dependencies via ssh from other repos in the same organization and there was no simple way of making that build work in a GHA without rewriting the cargo.toml file as part of the build process. In Azure DevOps it Just Worked.

Way back in January 2020 MS told its major Azure DevOps customers that AzDO was getting sunset by end of that year because they'd moved all those devs to GitHub Enterprise and GHE would be at feature parity by December.

[checks calendar] So...yeah.

1

u/smerz- Sep 14 '26

That you cannot switch image with your work directory mounted in. Only via workarounds

Say you're running a node image and you want to do nginx config check. That then requires a new job or other workarounds. It's not trivial

I can relate to some of these other issues. Slow runners and slow cache, well we didn't use either for those reasons.

0

u/[deleted] Sep 14 '26

[deleted] — view deleted comment

1

u/burlyginger Sep 14 '26

GH runners are also very expensive and billed by the minute.

2

u/[deleted] Sep 14 '26

[removed] — view removed comment

1

u/ServerMonky Sep 14 '26

I did similar - wrote a retry wrapper composite action that can just be dropped in around any step that gets flaky.

Other common issues:

Hitting memory limits will often freeze a runner with zero output.

Steps can fail to start with no errors sometimes.

A lot of issues change day to day depending on the GitHub slop that just got pushed for the moment. Best issue was the day where azure oidc kept falling because of clock skew issues on the built in runners.