I've duplicated the workflow, but not sure exactly how to test that this works as it should. I'd love some advice on how I can test this.

/ci-ginkgo

How will people remember to update the two workflows at the same time?

Well the idea was to initially get this workflow in and running, and then once we know it works, figure out how to dedup it.

Given that the triggers are the same as the Ginkgo workflow, would it make sense instead to extend the Matrix to run with the race images as well, rather than duplicating the workflow entirely?

I'm not very opinionated on this, perhaps @nbusseneau has some ideas?

I'd love some advice on how I can test this.

Not sure if it will work, but from your changes in the ariane-config.yaml, let's try /ci-gingko?

Oh, I wasn't sure that I could run workflows from a fork.

It will indeed not run from a fork, you will need to re-open your PR with a branch located on upstream :) I would suggest using a separate trigger in Ariane config to be able to trigger only that workflow, and there is a special trick you need to do to get your new workflow to register when you open the PR: add a temporary pull_request: {} trigger to the workflow, just to register the workflow on the repository when the PR opens. After it has been registered, you will be able to run the workflow with the Ariane trigger no problem, and can remove the pull_request: {} trigger.

As for structure: for testing let's just do it copy/pasted for now, when we are happy with how it works I would suggest we look into merging the changes in the main Ginkgo workflow file, so that only one file needs to be maintained. One idea I have is to leverage the extra-args parameters that Ariane allows, so we could trigger race pipelines with a trigger like this: /ci-ginkgo race.

Let me know if you need help with anything :)

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.