Open turion opened 4 months ago
Just so we're clear, compared to this output, what do you need?
(also you're not using the latest version, it's 0.1.7.0 now)
Ideally, it would print the output it just created. For example, it might cat $GITHUB_OUTPUT
. Then I can see immediately whether get-tested
produced the right matrix.
In my situation, I had another job that needed the output of get-tested
, but I forgot to specify a github actions dependency with needs:
, so it triggered the action too soon, when get-tested
wasn't done yet. This looked as if get-tested
had produced an incorrect JSON instead.
Got it, I'll take care of it around the end of next week because I'm neck-deep into other problems. If it's too long for you I'll gladly review a PR. :)
@turion As a workaround, you can run the "Generate matrix from cabal" job with debug logging enabled. Then the generated JSON shows up in the logs: https://github.com/mmhat/os-string-aeson/actions/runs/10343168770/job/28737038619#step:5:17
I often find myself debugging why it doesn't work as intended on Github Actions, which is cumbersome. It would be great if there was a verbose mode, or if
get-tested
would always produce debug output when used as an action. E.g. when I look at this:https://github.com/turion/time-domain/actions/runs/9665355746/job/26662232443?pr=21#step:2:134
I can't really see what the output of the run was. If it could just echo that, it would already be helpful.