Problem statement
We have a CI that is configured to run on pull_request events on all branches: https://github.com/Kong/kubernetes-ingress-controller/blob/beac200706f81b9420d21b00653fd59a4040f8bb/.github/workflows/pr_checks.yaml#L12-L14.
Given an exemplar PR Kong/kubernetes-ingress-controller#4128 that got a label to be backported to release/2.10.x branch we received this PR Kong/kubernetes-ingress-controller#4131 which triggered only pull request labelled event not pull_request as it should. Hence we didn't get a full CI run as we'd like to: https://github.com/Kong/kubernetes-ingress-controller/actions?query=branch%3Abackport-4128-to-release%2F2.10.x
Expected behavior
PRs created by this action trigger pull_request event so that a full CI run can be triggered.
Problem statement
We have a CI that is configured to run on
pull_requestevents on all branches: https://github.com/Kong/kubernetes-ingress-controller/blob/beac200706f81b9420d21b00653fd59a4040f8bb/.github/workflows/pr_checks.yaml#L12-L14.Given an exemplar PR Kong/kubernetes-ingress-controller#4128 that got a label to be backported to
release/2.10.xbranch we received this PR Kong/kubernetes-ingress-controller#4131 which triggered only pull request labelled event notpull_requestas it should. Hence we didn't get a full CI run as we'd like to: https://github.com/Kong/kubernetes-ingress-controller/actions?query=branch%3Abackport-4128-to-release%2F2.10.xExpected behavior
PRs created by this action trigger
pull_requestevent so that a full CI run can be triggered.