84
GitHub Actions Is Slowly Killing Your Engineering Team - Ian Duncan (www.iankduncan.com)
submitted 7 months ago by to c/programming@programming.dev
29 comments fedilink hide all child comments
 

Why GitHub Actions is the Internet Explorer of CI, and why Buildkite offers a better path forward for teams that care about developer experience.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 7 months ago* (3 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 7 months ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 7 months ago (1 child)

    Time to look for a better boss

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent