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
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.)
yaroto98@lemmy.world 3 days 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.