getchoo
commented
10 months ago after attempting something similar and even digging into the payload sent from check suite completion, there still doesn't seem to be a good way to get around this. i found a related discussion though, and it was mentioned that a possible solution could be to trigger a repository_dispatch event with a specific event_type. something like this would allow for much better integrations with "follow up" post-build workflows - like in the case of continuous delivery. this would also hopefully only be delivered once all builds have completed
i've started using garnix recently, and the experience has been great! one of the only issues i've come across though was with the github actions integration - as described here. it seems that after the flake is initially evaluated, workflows can be triggered without the subsequent checks being completed due to that initial check reporting the whole suite as succeed before adding the specified outputs from
garinx.yaml. i'm not sure if this is a limit of the statuses api as i'm not very familiar familiar, but it messes up my workflows a bit since i would prefer to use the cached builds of my flake outputs from garnix in the subsequent github workflow, and of course only have one workflow triggered per run instead of two.below is a reference from a webhook for one of my repos in a discord channel (the first workflow triggered by the flake evaluation being finished was cancelled manually)