83
GitHub Actions Is Slowly Killing Your Engineering Team - Ian Duncan
(www.iankduncan.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Mar 2026
83 points (94.6% liked)
Programming
26276 readers
175 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
If you can get the permissions to do it set the protected branch and prevent merge on build failures. This is a repo setting that will work with any ci provider assuming it updates the PR status.
I thought about it but people are so sensitive here. If they broke something and couldn't merge they'd probably raise a big stink, and then there's good odds the checks would be removed "because they're adding friction" or some nonsense. My boss has already warned me about staying in my lane.
These people have never done any automated testing of any sort. No linter. No unit tests. And they don't seem to want to.
Time to look for a better boss
Well, yes, though my direct manager isn't the worst. He's trying to protect me from other teams that might get pissy.
One of my friends is a product manager type and his analysis was basically "if stakeholders don't care it's not a problem, even if by any reasonable metric it is a problem". So. Here we are.