Open hartwork opened 8 months ago
Definitely. We are going to be using prow
as part of our CI for the entire organization, and this will be managed in a similar way.
Thank you for noticing and reporting this!
@NeilHanlon use of prow sounds a like a bigger migration? I think before a migrating to prow all it would take if wanted would be to:
pull_request
to https://github.com/openela/openela.org/blob/92fe9fde5bba04e654ac2dd269a05e05be6f558f/.github/workflows/hugo.yaml#L3deploy
from pull requests (probably by adding a condition)Just an idea.
You're right. I'll get to this today :)
Hi!
The CI at https://github.com/openela/openela.org/blob/main/.github/workflows/hugo.yaml seems to only run when (a) pushed to
master
or (b) when manually triggered but not for pull requests. In that current setup, it will be possible for pull requests to breakmaster
and only notice that after merge. Is that beneficial and intended?Best, Sebastian