Ricky Curtice

What is the progress on building the tests and applying the pull? These are pretty critical events - especially the close event!

There does not appear to be. And yes, it's quite annoying to clean up afterwards. In my case I'm not using a matrix, I'm instead using one job per OS...

I prefer to have the release created only if at least one of the builds succeeded. In fact I'd prefer that it only happened if all builds succeeded. But that's...

Bumping this both here and there. Being able to read the tags would be a very nice feature and it looks like this might have been lost in the woodwork.

Methinks PioBeat was meaning that the generated CMake files would be able to have the conan integration lines pre-included. However there's more than one way to do so: https://docs.conan.io/en/latest/integrations/build_system/cmake.html

The conanfile stores the dependency information. See https://github.com/HalcyonGrid/aperture/blob/master/conanfile.txt for one I created. It’s typically managed using the Conan CLI tooling and does not have to be auto generated. However I’d...

Fora workflow run I simply wrote two steps in my job: one reports success, the second has if:failure() and reports that there was a problem. Both use the above linked...

As you can see from https://github.com/aws-actions/amazon-ecs-deploy-task-definition/tags currently `v1` and `v1.4.7` point to the same commit. But if you wanted to lock to a specific version then just reference the version...

I got a workaround solved as follows: ```yaml - name: Install NUnit run: | nuget install NUnit.Console -Version 3.12.0 - name: Fetch transform code run: | wget https://raw.githubusercontent.com/nunit/nunit-transforms/master/nunit3-junit/nunit3-junit.xslt shell: bash...

Excellent. In my case the generation of the xml was split into a different workflow than the analysis of it. Since I prefer that the untransformed file be placed in...