46
I Hate Github Actions with Passion (xlii.space)
submitted 9 months ago by to c/technology@lemmy.world
27 comments fedilink hide all child comments
 

I can’t overstate how much I hate GitHub Actions. I don’t even remember hating any other piece of technology I used. Sure, I still make fun of PHP that I remember from times of PHP41, but even then I didn’t hate it. Merely I found it subpar technology to other emerging at the time (like Ruby on Rails or Django). And yet I hate GitHub Actions.
With Passion2.

Road to Hell
Day before writing these words I was implementing build.rs for my tmplr project. To save you a click - it is a file/project scaffold tool with human readable (and craftable) template files. I (personally) use it very often, given how easy it is to craft new templates, by hand or with aid of the tool, so check it out if you need a similar tool.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 9 months ago (2 children)

There's not to my knowledge a good way to run/test GitHub actions locally. So if I want to verify my change uploads the coverage report after the end of the pipeline, I have to run the whole thing. And then I find an error because on the GitHub runner blah blah is different

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 9 months ago

    You can install the github actions runner locally and use it, however all that does is eat your cpu cycles and prevent them from charging you. It doesn't help you debug that blackbox at all.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 9 months ago

    The best way I found to do this is by commenting out the portions of the build that take the longest.

    Which is stupid, but that's what you get with Microsoft products.

    (I get that there may be ways to test this locally, but I found this method to be the easiest.)

  • permalink
  • fedilink
  • source
  • parent