Skip to content

Commit 007d0b1

Browse files
chore(ci): re-trigger CI after a label event produced a no-op run
The latest run on this head came from a `labeled` event carrying a label other than full-e2e. pull-requests.yaml discards those by design — `plan` skips, and checks, build, build-talos, finalize and e2e all skip behind it — so the run reported nothing. Two side effects made that worse than a wasted run: the required "E2E Tests" context was left SKIPPED, which branch protection counts as satisfied, and cancel-in-progress killed the in-flight api-review-gate run that was carrying the real signal. Empty commit to get a genuine run against this head. No content change. Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 2330d6f commit 007d0b1

0 file changed

File tree

    0 commit comments

    Comments
     (0)